| From: | Markus Kräutner <kraeutne(at)in(dot)tum(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Possible bug in update? |
| Date: | 2003-08-28 10:28:30 |
| Message-ID: | 200308281228.30356.kraeutne@in.tum.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > At the end of several bulk inserts the following statements get executed:
> >
> > begin
> > update pom_c2996785 set p3=3268837857008 where p3=34804837857008
> > update pom_c2996795 set p3=3268837857008 where p3=34804837857008
> > update pom_c2996804 set p3=3268837857008 where p3=34804837857008
> > commit
> >
> > When I check the database the last update has not been executed. Manually
> > executing it in psql does work.
>
> ... ergo, the bug is not in the backend, but in whatever non-psql client
> software you are using. Since you haven't mentioned what that is,
> further speculation is difficult ...
I managed to construct a sample script which also fails in psql. It seems to
be the hash index. If I leave out the "create index" line or use btree
instead everything works fine.
I will use btree now :)
Thank you for your help.
Markus
| Attachment | Content-Type | Size |
|---|---|---|
| pom1.log.gz | application/x-gzip | 7.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2003-08-28 10:43:29 | Linux2.6 overcommit behaviour |
| Previous Message | Dave Cramer | 2003-08-28 10:28:16 | suspicous looking code in copy.c |