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"?
The best thing about modern society is how easy it is to avoid contact with it.
In response to
pgsql-hackers by date
|Next:||From: Jeff Janes||Date: 2012-01-30 15:48:34|
|Subject: Re: Simulating Clog Contention|
|Previous:||From: Andrew Dunstan||Date: 2012-01-30 15:37:06|
|Subject: Re: JSON for PG 9.2|
pgsql-general by date
|Next:||From: Tom Lane||Date: 2012-01-30 16:12:09|
|Subject: Re: pg_dump -s dumps data?! |
|Previous:||From: Adrian Klaver||Date: 2012-01-30 15:34:49|
|Subject: Re: pg_dump -s dumps data?!|