Re: Corner case in xlog stuff: what happens exactly at a seg boundary?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Corner case in xlog stuff: what happens exactly at a seg boundary?
Date: 2006-08-07 19:46:23
Message-ID: 14140.1154979983@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> Should we ask users if anyone is currently doing this? It seems pretty
> ugly to have most functions return the last used WAL byte with only
> stop_backup returning the first unused byte.

No, you misunderstood. All the functions that return WAL location
strings use the same convention. It's the two new functions that
convert a WAL location string to a filename that have the boundary-case
logic.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Constantin Teodorescu 2006-08-07 20:02:42 PostgreSQL performance enhancement when query planner fails to guess the right plan
Previous Message Josh Berkus 2006-08-07 19:45:27 Re: Intermittent "make check" failures on hyena