Tom Lane escribió: > Alvaro Herrera <alvhe...@commandprompt.com> writes: > > Kevin Grittner escribi�: > >> Robert Haas <robertmh...@gmail.com> wrote: > > Tom Lane <t...@sss.pgh.pa.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. > > Well, the subtext of my comment was really that this case isn't useful > enough to justify introducing a nonstandard construct into dumps.
That's true, but this is not the first time we've left out some feature from dumps because they would make them standards-incompatible. If we have enough of these (and I have no idea that we do), maybe we could start here. This is of course just a future TODO item, not something to consider for 9.0. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
