| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Michael Adler <adler(at)pobox(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: invalidating cached plans |
| Date: | 2005-03-15 01:34:00 |
| Message-ID: | 42363B88.3060908@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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."
You can go 'SET TRANSACTION READ ONLY;' or something...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2005-03-15 01:37:09 | Re: invalidating cached plans |
| Previous Message | Qingqing Zhou | 2005-03-15 01:25:33 | Re: invalidating cached plans |