Re: invalidating cached plans - Mailing list pgsql-hackers

From Michael Adler
Subject Re: invalidating cached plans
Date
Msg-id 20050314170142.GB21867@pobox.com
Whole thread Raw
In response to Re: invalidating cached plans  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: invalidating cached plans
Re: invalidating cached plans
List pgsql-hackers
On Mon, Mar 14, 2005 at 02:53:36AM -0500, Tom Lane wrote:
> Probably the first thing to do is look around at the plausible users of
> this thing and see what they'd find most convenient.

This may be totally irrelevant:

Our current load distributors, like pgpool, have no way of knowing the
side effects of backend functions. It would be interesting if the
client could send each potential query to the master saying, "execute
this query if there are side effects, otherwise do no operation and
and let me execute this read-only query on a replicated copy."
-Mike


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: signed short fd
Next
From: Tom Lane
Date:
Subject: Avoiding tuple construction/deconstruction during joining