Prev: trace_recovery_messages
Next: [HACKERS] system views for walsender activity
From: Andres Freund on 17 Jun 2010 18:44
Hi,

On Friday 18 June 2010 00:22:00 Josh Berkus wrote:
> We've noticed that checksums and file sizes for the master database, and
> slave database, even after all transactions have been cleared, are not
> identical. Why is that?
Non Wal-Logged action like visibility bits.

Andres

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Andrew Dunstan on 17 Jun 2010 19:05


Tom Lane wrote:
> Andres Freund <andres(a)anarazel.de> writes:
>
>> On Friday 18 June 2010 00:22:00 Josh Berkus wrote:
>>
>>> We've noticed that checksums and file sizes for the master database, and
>>> slave database, even after all transactions have been cleared, are not
>>> identical. Why is that?
>>>
>
>
>> Non Wal-Logged action like visibility bits.
>>
>
> That wouldn't affect file sizes though. Could we have some specifics?
>
>
>

I have not noticed different file sizes, only checksums.

cheers

andrew

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 17 Jun 2010 19:00
Andres Freund <andres(a)anarazel.de> writes:
> On Friday 18 June 2010 00:22:00 Josh Berkus wrote:
>> We've noticed that checksums and file sizes for the master database, and
>> slave database, even after all transactions have been cleared, are not
>> identical. Why is that?

> Non Wal-Logged action like visibility bits.

That wouldn't affect file sizes though. Could we have some specifics?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: trace_recovery_messages
Next: [HACKERS] system views for walsender activity