Re: Immodest Proposal: pg_catalog.pg_ddl - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Immodest Proposal: pg_catalog.pg_ddl
Date
Msg-id 43A038B4.7010004@dunslane.net
Whole thread Raw
In response to Re: Immodest Proposal: pg_catalog.pg_ddl  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Immodest Proposal: pg_catalog.pg_ddl  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:

>
>>Simple.  Postmaster logs can roll over or otherwise be lost without
>>damaging the DB.  This would provide a non-volatile log of DDLs.
>>    
>>
>
>In that case you have to provide a pretty strong argument why everyone
>should be forced to have a non-volatile log of DDLs.  
>  
>

Conversely, why *only* DDL. As soon as we had this there would be a very 
strong demand to log DML.

Maybe we need an optional asynch logging process as yet another member 
of our growing band of specialist background processes.

What I would like to see is some builtin functions that give me the 
table's DDL, just as pg_dump does. Extra nice would be complementary 
functions that also give me skeleton select statements for each table or 
view. I used to use such facilities a lot in years gone by, along with 
c&p - maybe I'm just old-fashioned.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql and COPY BINARY
Next
From: Tom Lane
Date:
Subject: Re: Immodest Proposal: pg_catalog.pg_ddl