Re: [PATCH 11/14] Introduce wal decoding via catalog timetravel

Andres Freund <andres@2ndquadrant.com>

From: Andres Freund <andres@2ndquadrant.com>
To: Steve Singer <steve@ssinger.info>
Cc: pgsql-hackers@postgresql.org
Date: 2012-12-03T14:48:10Z
Lists: pgsql-hackers
On 2012-12-03 09:35:55 -0500, Steve Singer wrote:
> On 12-12-03 07:42 AM, Andres Freund wrote:
> >Two things:
> >1) Which exact options are you using for pg_receivellog? Not "-d
> >replication" by any chance?
>
> Yes that is exactly what I'md doing.  Using a real database name instead
> makes this go away.

Was using "replication" an accident or do you think it makes sense in
some way?

Greetings,

Andres Freund

--
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Background worker processes

  2. Rearrange storage of data in xl_running_xacts.

  3. Basic binary heap implementation.

  4. Embedded list interface

  5. Refactor xlog.c to create src/backend/postmaster/startup.c