| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WAL Info messages |
| Date: | 2009-12-13 20:36:06 |
| Message-ID: | 28182.1260736566@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> Proposal is to use up the last rmgr id, slot 7: RM_INFO_ID.
> Functions would be provided on primary side to send a user-defined
> binary message into WAL stream, with a single message type
> XLOG_INFO_MSG. (Superuser only, though can be wrapped and given to
> trusted users).
Seems like a frammish that we could maybe worry about a few months from
now, after the core patch has settled down.
I also dislike reserving a whole RM_ID just for this. If we are only
going to send one type of message it seems like it could be one infomask
type within an existing RM_ID.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-13 20:45:54 | Re: Hot Standby, release candidate? |
| Previous Message | Robert Haas | 2009-12-13 20:30:04 | Re: WAL Info messages |