Skip site navigation (1) Skip section navigation (2)

Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Hartmut Goebel <h(dot)goebel(at)goebel-consult(dot)de>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
Date: 2010-06-10 14:30:46
Message-ID: 15929.1276180246@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> That is exactly what I think is "to big a promise" - I don't think we 
> can actually guarantee that this will fix the dump/restore issue (well 
> the dump might load but say the 30000 lines of plpgsql using dynamic SQL 
> will still be broken).

Yeah, that's a mighty good point.  We are certainly not going to try to
fix the contents of function bodies.  The only things we could possibly
fix that we don't handle today (when using the newer pg_dump) are
references in views, check constraint expressions, etc.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-06-10 14:34:35
Subject: Re: Beta 2 build issue
Previous:From: Thom BrownDate: 2010-06-10 14:27:51
Subject: Beta 2 build issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group