> There's probably not much more we can learn at this point --- given
> that the entry is old, any other evidence is probably long gone.
I'm afraid I'll never be able to get soon enough to the evidence even if
it happens again, unless I manage to reproduce it myself, which I tried
but didn't succe
Csaba Nagy <[EMAIL PROTECTED]> writes:
>> Is this xmin quite a bit older than what you get for a freshly-created
>> temp table?
> I would say yes, this is a test system which is highly stressed from
> time to time, but does not get continuous load.
OK, so it seems we have an old pg_type entry t
> Is this xmin quite a bit older than what you get for a freshly-created
> temp table?
I would say yes, this is a test system which is highly stressed from
time to time, but does not get continuous load.
test03=> select oid, xmin from pg_type where typname = 'temp_report';
oid| xmin
--
Csaba Nagy <[EMAIL PROTECTED]> writes:
> I executed what you suggest below, see the results below. Short
> conclusion: the type is there in pg_type, the relation is not there in
> pg_class. Is there anything I should look for more ?
> test03=> select oid, xmin from pg_type where typname = 'temp_re
On Fri, 2006-09-01 at 11:25, Csaba Nagy wrote:
> I executed what you suggest below [snip]
Ok... it looks like the postgres version is not what I expected and
reported in the first mail, but:
test03=> select version();
version
I executed what you suggest below, see the results below. Short
conclusion: the type is there in pg_type, the relation is not there in
pg_class. Is there anything I should look for more ?
Cheers,
Csaba.
> BTW, when this happens, does the error persist? If it's a race
> condition you'd expect not
Csaba Nagy <[EMAIL PROTECTED]> writes:
> create temp table temp_report ...;
> ... do some processing using this table...
> drop table temp_report;
> commit;
> This code occasionally triggered the following error (couldn't reliably
> reproduce):
> ERROR: type "temp_report" already exists
B
Csaba Nagy <[EMAIL PROTECTED]> writes:
> In any case, the error message is strange in itself, as if I try to
> create the temporary table when it exists, the error I get in manual
> trial is:
> ERROR: relation "test_temp_table" already exists
>
> compared to the error from the OP
Csaba Nagy wrote:
In any case, the error message is strange in itself, as if I try to
create the temporary table when it exists, the error I get in manual
trial is:
ERROR: relation "test_temp_table" already exists
compared to the error from the OP which I cite here for referen
On Thu, 2006-08-31 at 17:25, Alban Hertroys wrote:
> Csaba Nagy wrote:
> > The code is possible to be executed in parallel by multiple threads, on
> > different connections, or in sequence on the same connection. I would
> > expect it in both cases to work correctly... in manual tests I was able
>
Csaba Nagy wrote:
The code is possible to be executed in parallel by multiple threads, on
different connections, or in sequence on the same connection. I would
expect it in both cases to work correctly... in manual tests I was able
to create in parallel temporary tables named identically in diffe
Postgres version: 8.1.3
I have a code similar to this pseudo-code:
try {
create temp table temp_report ...;
... do some processing using this table...
drop table temp_report;
commit;
} catch all errors {
rollback;
}
This code occasionally triggered the following error (couldn't reliabl
12 matches
Mail list logo
