| From: | Joshua Bay <joshuabay93(at)gmail(dot)com> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Logical decoding |
| Date: | 2016-07-08 17:57:02 |
| Message-ID: | CABb-U3YYmhRPFc5RJ5OVL-CwEzVLZLc-rcPGcLWPLJeWJVBQPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Hi,
I have a question about logical decoding of Postgres.
where are the entry points to logical decoding?
Specifically, we want to know whether logical decoding happens immediately
after commit, or whether there is a polling thread that scans the Write
Ahead Log and then dumps to the special table?
and where are this code is in the codebase?
Thanks,
Joshua
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-07-08 18:32:35 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Previous Message | Andres Freund | 2016-07-08 17:53:49 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shoaib Lari | 2016-07-08 17:58:07 | Fix Error Message for allocate_recordbuf() Failure |
| Previous Message | Andres Freund | 2016-07-08 17:53:49 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |