| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NOTIFY/LISTEN on read-only slave? |
| Date: | 2010-02-18 03:05:08 |
| Message-ID: | 4B7CAE64.1020706@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>
>> Our documentation says listen/notify will return an error if executed on
>> the hot standby server:
>>
>> o LISTEN, UNLISTEN, NOTIFY since they currently write to system tables
>>
>> With the listen/notify system now implemented in memory, is this still
>> true?
>>
>
> The explanation is wrong, but it's still disallowed.
>
What's the actual reason for the restriction then? I did a whole
proofreading round on the HS documentation the other day and am working
on a patch to clean up everything I found, can add better notes about
this to it.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-02-18 03:06:46 | Re: NOTIFY/LISTEN on read-only slave? |
| Previous Message | Andrew Dunstan | 2010-02-18 02:27:17 | Re: CommitFest Status Summary - 2010-02-14 |