From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Immodest Proposal: pg_catalog.pg_ddl |
Date: | 2005-12-14 04:43:10 |
Message-ID: | 20051214044310.GE7463@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 13, 2005 at 11:33:20PM -0500, Tom Lane wrote:
> David Fetter <david(at)fetter(dot)org> writes:
> > The idea is to make a new table in pg_catalog called pg_ddl.
>
> This seems rather poorly thought out --- I can't even tell whether
> your intention is to make a log of past operations,
Yes.
> or to provide a uniform way to extract the current definition of
> every object. If the latter, recording text won't do it. If the
> former, the notion that all DDL can be uniquely keyed to one object
> OID is bogus,
What could it be keyed to, then?
> and I don't even see the argument for doing it via a table rather
> than via the postmaster log.
Simple. Postmaster logs can roll over or otherwise be lost without
damaging the DB. This would provide a non-volatile log of DDLs.
It occurs to me that the creator's or in the case of ALTER, the
modifier's, rolename and oid should be along.
Thanks for the feedback :)
Cheers,
D
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 415 235 3778
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-12-14 08:17:31 | Re: lo function changed in PostgreSQL 8.1.1 |
Previous Message | Tom Lane | 2005-12-14 04:33:20 | Re: Immodest Proposal: pg_catalog.pg_ddl |