>
> Hi Justin,
Thank you for your reply..
> In the future please don't cross post to multiple lists.
Appoligies for it...
Regards
Raghavendra
On Sat, Apr 3, 2010 at 10:34 PM, jus...@magwerks.com
wrote:
> Because You dropped/deleted the table cache in Session A.
>
> The simplest way to loo
raghavendra t writes:
> I am facing the error "cache lookup failed for relation X" in Postgres-8.4.2
> [ when dropping the same table concurrently in two sessions ]
> Could plese tell me, why this is generated and what is the cause.
>From the perspective of session B, the table disappeared after
Because You dropped/deleted the table cache in Session A.
The simplest way to look at it is Session B was lock out when the Drop table
command was issued from Session A. Now when session B finally got its chance to
drop/delete the table it was already gone .
What kind error were you expecting f
Hi All,
I am facing the error "cache lookup failed for relation X" in Postgres-8.4.2
version. As you all know, its a reproducable and below is the example.
This can be generated with two sessions;
Am opening two sessions here Session A and Session B
Session A
=
step 1 - creating the table
Le 02/04/2010 22:10, Campbell, Lance a écrit :
> Greg,
> Thanks for your help.
>
> 1) How does the number of buffers provided by pg_buffercache compare to
> memory (buffers * X = Y meg)?
1 buffer is 8 KB.
> 2) Is there a way to tell how many total buffers I have available/max?
With pg_bufferc
