From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Neil Conway" <neilc(at)samurai(dot)com>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: adminpack and pg_catalog |
Date: | 2006-10-21 09:01:16 |
Message-ID: | 00f901c6f4ef$62e3191f$6a01a8c0@valehousing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----Original Message-----
From: "Neil Conway" <neilc(at)samurai(dot)com>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Sent: 20/10/06 21:19
Subject: Re: adminpack and pg_catalog
> It breaks in the sense of "completely not working" :)
No, it does not 'break pg_dump'. What you have shown is that pg_dump doesn't dump adminpack which is exactly what we want, and perfectly correct behaviour from pg_dump.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-10-21 09:37:51 | Re: xlogdump fixups and WAL log question. |
Previous Message | Dave Page | 2006-10-21 08:52:37 | Re: adminpack and pg_catalog |