| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Fwd: Start up question about triggers |
| Date: | 2006-06-26 18:24:45 |
| Message-ID: | 20060626182445.GD20519@phlogiston.dyndns.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, Jun 26, 2006 at 10:38:06AM -0500, Scott Marlowe wrote:
> I bet it would be possible to hack pgpool to do this. Just have it
> shoot all the queries that come in to it at the normal database, AND at
> a text file or something like that.
Now you're back to the same problem: it doesn't tell you what the
database looks like. It tells you what commands were sent. What
about triggers? Rules? For that matter, what about
SELECT now()
or
SELECT nextval()
?
--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well.
--Dennis Ritchie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremiah Elliott | 2006-06-26 21:22:11 | avg(interval) |
| Previous Message | Scott Marlowe | 2006-06-26 15:38:06 | Re: Fwd: Start up question about triggers |