> It does. The point is that the system is set up to limit the bad
>> consequences. You might (will) get wrong query answers, but the
>> heap data won't get corrupted.
if this is our goal - *"can return wrong query answers, but
should not corrupt the heap data.*" and if we make Thick indexes capable of
that, can i consider that as a thumbs up from your side? As you may already
know, this will only happen when there is a volatile function based index.
Please let me know, if you feel otherwise.
In response to
pgsql-hackers by date
|Next:||From: Josh Berkus||Date: 2010-02-26 21:06:10|
|Subject: Re: Hot Standby query cancellation and Streaming Replication
|Previous:||From: Tom Lane||Date: 2010-02-26 20:47:55|
|Subject: Re: Avoiding bad prepared-statement plans. |