Re: [HACKERS] Forcing current WAL file to be archived

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Hannu Krosing <hannu(at)skype(dot)net>
Subject: Re: [HACKERS] Forcing current WAL file to be archived
Date: 2006-08-16 15:45:53
Message-ID: 22114.1155743153@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> We want a single row output, with two columns, yes?
> Presumably:
> xlogfilename TEXT
> offset INTEGER

Sounds right to me. int4 should be wide enough for practical xlog
segment sizes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-08-16 16:36:24 timing psql internal commands
Previous Message Simon Riggs 2006-08-16 15:41:18 Re: [HACKERS] Forcing current WAL file to be archived

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-08-16 16:50:51 Re: selecting large result sets in psql using cursors
Previous Message Simon Riggs 2006-08-16 15:41:18 Re: [HACKERS] Forcing current WAL file to be archived