FWIW,
I have experienced some oddities in performing SELECT statements after
restarting on an 8.2 system, whereby I occasionally would get a ton of
duplicate records when I would do a select statement (my assumption is that
they are deleted tuples being returned). If I executed the same select
Hi Kevin,
Yeah I see exactly the same problem on 8.3.5 too, although it seems
random - what seems to happen is that sometimes the contents of the
temporary table disappears. I've attached a test script which causes the
error *some* of the time, although it tends to occur more often just
Mark Cave-Ayland [EMAIL PROTECTED] writes:
So in other words, the contents of the temporary table has just disappeared :(
Uhm. That rather sucks. I was able to reproduce it too.
It seems to happen after I pause for a bit, and not when I run the script in
fast succession.
--
Gregory Stark
Gregory Stark wrote:
Uhm. That rather sucks. I was able to reproduce it too.
It seems to happen after I pause for a bit, and not when I run the script in
fast succession.
Thanks for the verification Greg. I'm wondering if the GiST part is a
red herring, and in fact it is related to some
Robert W. Burgholzer [EMAIL PROTECTED] writes:
FWIW,
I have experienced some oddities in performing SELECT statements after
restarting on an 8.2 system, whereby I occasionally would get a ton of
duplicate records when I would do a select statement (my assumption is that
they are deleted
Mark Cave-Ayland wrote:
On Thu, 2008-12-04 at 13:51 -0800, Kevin Neufeld wrote:
Wow, that's bad. I just updated to PostgreSQL 8.3.5 from 8.3.3 and I now get
the same thing.
test=# create temp table tmp as select st_makepoint(random(), random()) as
the_geom from generate_series(1, 1);
