| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, SF Postgres <sfpug(at)postgresql(dot)org> |
| Subject: | Re: DDL triggers? |
| Date: | 2003-05-20 17:52:03 |
| Message-ID: | 20030520105039.M69760-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
On Tue, 20 May 2003, Josh Berkus wrote:
> David,
>
> > > Alternately, we can raise this on -Hackers and see what the
> > > difficulty would be for hacking some of the libraries to either:
> > >
> > > 1) save all DDL statements to a log, or:
> >
> > This would actually be a super-groovy thing in general, 'cause the
> > stuff pg_dump spits out, while useful from a reloading point of view,
> > is a royal PITA from a reverse-engineering point of view. Ideally,
> > DDL's would get logged in the precise state (ideally, with "--"'s
> > included) that they were in before they got executed.
>
> I think this would be relatively easy; in fact, I'm sure that Joe Conway could
> do it. Why don't you give him a buzz?
It should be easy presumably. You might be able to cheat right now if you
turn on statement logging and wrote a script to get them out of the logs.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2003-05-20 18:36:11 | Re: DDL triggers? |
| Previous Message | Josh Berkus | 2003-05-20 17:09:40 | Re: DDL triggers? |