how about saying:
lock table versions_9d in EXCLUSIVE mode;
UPDATE versions_9d SET flag=2;
commit;
Ismo
On Thu, 22 Feb 2007, Gabriel Biberian wrote:
> Hello,
>
> I experience significant performance issues with postgresql and updates.
> I have a table which contains ~1M rows.
> Layout:
> TOTO
Thanks to everyone for the feedback about vacuuming. It's been very
useful. The pointers to the pgstattuple and Pgfouine tools were also
helpful.
I'm now considering the following plan for trying Autovacuuming again
with 8.1. I'd like any peer review you have to offer of the following:
1. First,
On Thu, Feb 22, 2007 at 12:19:50PM -0800, Barbara Cosentino wrote:
> I have a table that gets many rows inserted, updated and then deleted,
> consistently throughout the day. At any point in time this table should
> have no more than 50 actual rows and many times a direct select against
> this tab
Hi,
Here is the situation. We are at postgres version 8.1.3.
I have a table that gets many rows inserted, updated and then deleted,
consistently throughout the day. At any point in time this table should
have no more than 50 actual rows and many times a direct select against
this table pr
n i tried adding an index to the table on the column date (int) that
> stores unix timestamps.
> TOTO=# CREATE INDEX versions_index ON versions_9d (date);
> (-60M) disk space goes down on index creation
> [EMAIL PROTECTED]:~$ time psql TOTO -c "UPDATE versions_9d SET flag=9"
> UPDATE 976009
> real
On Thu, Feb 22, 2007 at 07:11:42PM +0100, Gabriel Biberian wrote:
> Create a new DB and load a dump of the above database with 976009 rows,
> then i perform updates on the whole table. I recorded the time taken
> for each full update and the amount of extra disk space used. Each
> consecutive
Hello,
I experience significant performance issues with postgresql and updates.
I have a table which contains ~1M rows.
Layout:
TOTO=# \d versions_9d;
Table «public.versions_9d»
Colonne | Type | Modificateurs
++---
h
Konstantinos Krikellas wrote:
Hi,
I am trying to execute some queries in PostgreSQL that produce a large
number of results and I do not want to display the output (redirect it
to /dev/null). I have tried the psql client with \o /dev/null option,
JDBC and libpq functions, but all of them have to
Hi,
I am trying to execute some queries in PostgreSQL that produce a large
number of results and I do not want to display the output (redirect it
to /dev/null). I have tried the psql client with \o /dev/null option,
JDBC and libpq functions, but all of them have to buffer totally the
result before
