From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Fwd: Start up question about triggers
Date: Mon, 26 Jun 2006 14:24:45 -0400
Message-ID: <20060626182445.GD20519@phlogiston.dyndns.org> (raw)
In-Reply-To: <1151336286.4215.35.camel@state.g2switchworks.com>
References: <200606261359.k5QDxE2p004593@auth-smtp.hol.gr>
<1151336286.4215.35.camel@state.g2switchworks.com>
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@crankycanuck.ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well.
--Dennis Ritchie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Fwd: Start up question about triggers
In-Reply-To: <20060626182445.GD20519@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox