2011/2/22 Alvaro Herrera :
> Excerpts from Bruce Momjian's message of vie feb 18 23:41:18 -0300 2011:
>>
>> Is this a TODO item?
>
> Only to me, it seems.
looks like you suggestion get positive impact so far :-)
+1 to fix the bogosity output rather than waiting for 9.2 via a todo
>
>
> --
Excerpts from Bruce Momjian's message of vie feb 18 23:41:18 -0300 2011:
>
> Is this a TODO item?
Only to me, it seems.
--
Álvaro Herrera
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-hackers mailing list
Is this a TODO item?
---
Alvaro Herrera wrote:
> I just noticed that if I specify pg_resetxlog a timeline ID with the -l
> switch, it will display this value as "TimeLineID of latest checkpoint".
> Which is not really the tr
Alvaro Herrera writes:
> I wonder if pg_resetxlog should display the actual pg_control values in
> one section, and the values that would be set after a reset in a
> different section, so that it is extra clear.
Seems reasonable, although I'd suggest labeling the first section as
"Current pg_cont
I just noticed that if I specify pg_resetxlog a timeline ID with the -l
switch, it will display this value as "TimeLineID of latest checkpoint".
Which is not really the truth.
I wonder if pg_resetxlog should display the actual pg_control values in
one section, and the values that would be set afte
