Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling as - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling as
Date
Msg-id 412A9747.5060807@familyhealth.com.au
Whole thread Raw
Responses Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling as  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql-server: Rearrange pg_subtrans handling as  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-hackers
Just random speculation, but could we use a pg_subtrans-like setup to do 
row share locks?

ie. Store them in a sort of table to avoid the problems with limited 
shared memory size?

Chris


Tom Lane wrote:

> Log Message:
> -----------
> Rearrange pg_subtrans handling as per recent discussion.  pg_subtrans
> updates are no longer WAL-logged nor even fsync'd; we do not need to,
> since after a crash no old pg_subtrans data is needed again.  We truncate
> pg_subtrans to RecentGlobalXmin at each checkpoint.  slru.c's API is
> refactored a little bit to separate out the necessary decisions.



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: debuging postgres
Next
From: Neil Conway
Date:
Subject: compile warnings in HEAD