Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: intercepting WAL writes


  • From: Jeff Davis <pgsql(at)j-davis(dot)com>
  • To: Mike <mike(at)fonolo(dot)com>
  • Cc: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: intercepting WAL writes
  • Date: Wed, 28 May 2008 17:25:24 -0700
  • Message-id: <1212020724(dot)7654(dot)4(dot)camel(at)dogma(dot)ljc(dot)laika(dot)com>

On Wed, 2008-05-28 at 19:11 -0400, Mike wrote:
> Can somebody point to the most logical place in the code to intercept
> the WAL writes? (just a rough direction would be enough)- or if this
> doesn’t make sense at all, another suggestion on where to get the
> data? (I’m trying to avoid doing it using triggers).

Why are you avoiding triggers? One solution might be to use Slony to
just create the log, and then read the log of events into memcached
rather than another PostgreSQL instance.

http://slony.info/documentation/logshipping.html

Those logs might be easier to process than the WAL.

Also, why do you need to intercept the WAL writes, and not just read
from a WAL archive? Does this need to be synchronous?

Regards,
	Jeff Davis




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group