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

Steve Singer <steve@ssinger.info>

From: Steve Singer <steve@ssinger.info>

To: Andres Freund <andres@2ndquadrant.com>

Cc: pgsql-hackers@postgresql.org

Date: 2012-12-03T14:35:55Z

Lists: pgsql-hackers

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.

Thanks

> This seems to produce exactly that kind off error messages. I added some
> error checking around that. Pushed.
>
> Thanks!
>
> 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 →

Background worker processes
- da07a1e85651 9.3.0 cited
Rearrange storage of data in xl_running_xacts.
- 5c11725867ac 9.3.0 cited
Basic binary heap implementation.
- 7a2fe9bd0371 9.3.0 cited
Embedded list interface
- a66ee69add6e 9.3.0 cited
Refactor xlog.c to create src/backend/postmaster/startup.c
- 9aceb6ab3c20 9.2.0 cited