| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_restore --single-transaction and --clean |
| Date: | 2010-02-10 16:30:30 |
| Message-ID: | 20100210163030.GG4922@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner escribió:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> >> We try to avoid using nonstandard SQL in dumps.
> >
> > How often do we succeed? It seems unlikely that our dumps would
> > be restorable into any other database.
>
> When we were running in a mixed environment we had several occasions
> where it was useful to feed pg_dump --column-inserts output into
> Sybase databases. It was very nice to have that. I think we did
> sometimes have to filter it through sed to deal with BOOLEAN vs BIT
> issues.
Maybe we should have a --compatible-mode or some such that enables these
things, instead of staying away from useful PG-only features.
The problem would then be how to test it ...
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2010-02-10 16:32:47 | Re: Some belated patch review for "Buffers" explain analyze patch |
| Previous Message | Kevin Grittner | 2010-02-10 16:27:15 | Re: pg_restore --single-transaction and --clean |