| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, 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 15:01:01 |
| Message-ID: | 16534.1276182061@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> To this point, and perhaps to the other regarding VIEW definitions to
> some extent, while the solution would move us from 80% to 90% of "things
> in PG that might cause a restore from an older pg_dump to fail", I think
> another metric we should consider is "% of our user base, particularly
> those more junior, that would benefit". I feel that number to be >10%,
> and growing. Additionally, those that this would really help are the
> same people who don't have complex views and/or stored procedures.
Um, I rather doubt that experience level has much of anything to do with
one's probability of getting blindsided by new SQL syntax.
regards, tom lane
PS: unless your definition of "experienced" is "sits on the SQL standards
committee" ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-06-10 15:01:14 | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
| Previous Message | Stephen Frost | 2010-06-10 14:56:03 | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |