| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump -s dumps data?! |
| Date: | 2012-01-30 15:39:13 |
| Message-ID: | 20120130153913.GA8224@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Jan 30, 2012 at 07:34:49AM -0800, Adrian Klaver wrote:
> Breaks certain cases when using pg_dump -s. Some of what you highlight above is
> designed behavior. What is happening is covered by my second rule of life 'Easy
> is difficult'. In this case it is the desire for a built in 'packaging' system
> that makes extending Postgres easier for the end user. To get that leads to
> more complexity in the backend and a new learning curve for those that have to
> deal with it.
not sure what "learning curve" you have in mind, since it simply
cripples functionality of pg_dump.
how steep is the learning curve, to learn that you no longer can make
sensible "pg_dump -s"?
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-01-30 16:12:09 | Re: pg_dump -s dumps data?! |
| Previous Message | Adrian Klaver | 2012-01-30 15:34:49 | Re: pg_dump -s dumps data?! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-01-30 15:48:34 | Re: Simulating Clog Contention |
| Previous Message | Andrew Dunstan | 2012-01-30 15:37:06 | Re: JSON for PG 9.2 |