This is strange and as of now I do not have a reliable way of reproducing.
Nevertheless,
either there is a major blunder on my side that urgently needs being
pointed at and eliminated
or there is something really strange with PG.
Short version:
I update some rows of a table changing non-primary k
Hello
2011/8/17 Rainer Pruy :
> This is strange and as of now I do not have a reliable way of reproducing.
> Nevertheless,
> either there is a major blunder on my side that urgently needs being
> pointed at and eliminated
> or there is something really strange with PG.
>
> Short version:
>
> I upd
Hallo,
this is strange for sure. The database is in heavy use regularly.
So it is - if at all - a rare occurrence.
The update statement reported 346305 updated rows.
And I could verify that this is the number of rows that hat there value
change
(where afterwards there was a "new" version in the ta
2011/8/17 Rainer Pruy :
> Hallo,
> this is strange for sure. The database is in heavy use regularly.
> So it is - if at all - a rare occurrence.
>
> The update statement reported 346305 updated rows.
> And I could verify that this is the number of rows that hat there value
> change
> (where afterwa
The following bug has been logged online:
Bug reference: 6166
Logged by: Alex Soto
Email address: aps...@gmail.com
PostgreSQL version: 9.0.4
Operating system: Linux (CentOS release 5.0 (Final))
Description:configure from source fails with 'This platform is not
thread-
"Alex Soto" writes:
> I was trying to build the 9.0.4 source tarball as the postgres user on a
> test machine.
> The configure step failed with the error:
> This platform is not thread-safe. Check the file 'config.log' or compile
> and run src/test/thread/thread_test for the exact reason.
> Use
Alex Soto writes:
> Here's the section in the config.log in case it makes a difference
> configure:28808: ./conftest
> Could not create file in /tmp or
> Could not generate failure for create file in /tmp **
> exiting
> configure:28812: $? = 1
> configure: program exited with status 1
[ greps...
The following bug has been logged online:
Bug reference: 6167
Logged by: Jesper Engman
Email address: jes...@engman.net
PostgreSQL version: 8.3.10
Operating system: Linux
Description:pg_dump fails on table lock
Details:
I have tables that exists for short time perio
