Skip site navigation (1) Skip section navigation (2)

Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Date: 2005-12-29 14:35:27
Message-ID: 1135866927.61038.13.camel@home (view raw or flat)
Thread:
Lists: pgsql-hackers
> So, my thinking would be to separate things into two:
> a) Add a TODO item "shared temp tables" that caters for (1) and (4)
> 
> 	ALTER TABLE name RELIABILITY 
> 		{DELETE ROWS AT RECOVERY | FULL RECOVERY}
> (syntax TBD)

DELETE ROWS AT RECOVERY would need to be careful or disallowed when
referenced via a foreign key to ensure the database is not restored in
an inconsistent state.

-- 


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2005-12-29 15:10:40
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous:From: Andrew DunstanDate: 2005-12-29 14:31:08
Subject: Re: localization problem (and solution)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group