| From: | rohit(dot)guptakec(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #8381: data base inconsistancy |
| Date: | 2013-08-11 08:06:55 |
| Message-ID: | E1V8Qfv-0006w8-3a@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 8381
Logged by: Rohit Gupta
Email address: rohit(dot)guptakec(at)gmail(dot)com
PostgreSQL version: Unsupported/Unknown
Operating system: linux
Description:
Background:- There were a large no. of INSERT/UPDATE/DELETE operation being
performed on DB. The DB is reindex/vacuum every hour.
During reindex/vacuum time one of the DB table value was successfully
updated. But later the read query after ~30 seconds read previous values. Is
this possible that the update query commit is delayed ? Are there are some
known issues of commit during reindex/vacuum.
Currently we are using DB version 8.1
Later when we check the DB status (after some days)it was having the correct
updated values.
We are using default isolation level (Read Committed)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Chmelar | 2013-08-11 09:23:21 | Re: BUG #8329: UPDATE x SET x.y = x.y + z does not work in PL/pgSQL |
| Previous Message | Peter Geoghegan | 2013-08-11 01:00:51 | Re: pg_stat_statements produces multiple entries for a single query with track = 'top' |