Re: [GENERAL] Postgresql vs. aggregates

[EMAIL PROTECTED] writes: I'd find all this much easier to reason about if I understood how the versions of a row are organized and accessed. How does postgresql locate the correct version of a row? It doesn't, particularly. A seqscan will of course visit all the versions of a row, and an

Re: [GENERAL] pg_dump and schema namespace notes

Bruce Momjian [EMAIL PROTECTED] writes: Any comments on this? It seems like a valid confusion. What solutions are there? I think we're stuck. We can't avoid the fact that the SQL syntax uses the keyword SCHEMA to mean a namespace. We also can't avoid the very common usage of database schema

[GENERAL] Record order change after update

Hello list, After update a column on a table, that row goes to the top when I do a select from that table without any order, is that the expected behavior in postgresql? is there a way to prevent it? Thanks in advance. Josué Maldonado ---(end of

Re: [GENERAL] Postgresql vs. aggregates

[EMAIL PROTECTED] wrote: But that raises an interesting idea. Suppose that instead of one summary row, I had, let's say, 1000. When my application creates an object, I choose one summary row at random (or round-robin) and update it. So now, instead of one row with many versions, I have 1000 with

[GENERAL] How to tell when postmaster is ready

I'm writing a small test harness. I have two threads. One that starts the postmaster and another that does all the testing and finally stops the postmaster with a pg_ctl stop. At present, the second thread starts with a sleep sufficient to ensure that the postmaster is running. Is there a

Re: [GENERAL] Postgresql vs. aggregates

Hi, - Original Message - From: Richard Huxton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Scott Marlowe [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, June 10, 2004 8:03 AM Subject: Re: [GENERAL] Postgresql vs. aggregates [EMAIL PROTECTED] wrote: But that raises an interesting

[GENERAL] VACUUM FULL produce warnings

look please http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253295 ---(end of broadcast)--- TIP 8: explain analyze is your friend

[GENERAL] Selecting reals into doubles

I have attached some SQL which produces what to me, at least, is rather unexpected results. Selecting real columns into double precision columns loses some precision. Is this expected or documented anywhere? Thanks, DROP TABLE precision_test; DROP TABLE precision_test2; CREATE TABLE

Re: [GENERAL] How to tell when postmaster is ready

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 10 June 2004 09:10, Thomas Hallgren wrote: I'm writing a small test harness. I have two threads. One that starts the postmaster and another that does all the testing and finally stops the postmaster with a pg_ctl stop. At present, the

Re: [GENERAL] How to tell when postmaster is ready

Thomas Hallgren wrote: I'm writing a small test harness. I have two threads. One that starts the postmaster and another that does all the testing and finally stops the postmaster with a pg_ctl stop. At present, the second thread starts with a sleep sufficient to ensure that the postmaster is

[GENERAL] Transactions and insertion ordering

Hi, I'm trying to work out how to make sure things are read from a table in a consistent order. The table represents a queue of items and also the history of those items. Even with serializable transaction isolation I can begin two transactions, insert a record in each, commit the second

Re: [GENERAL] PostgreSQL insert speed tests

Tom Lane wrote: Sezai YILMAZ [EMAIL PROTECTED] writes: Tom Lane wrote: The slowdown you report probably is due to the rewrite of hash indexing to allow more concurrency --- the locking algorithm is more complex than it used to be. I am surprised that the effect is so large though.

[GENERAL] Can't compile a contrib util: dbsize (probably simply though)

Hello pgsql-general, When I am running make I get the following: gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I. -I~/postgresql-7.4.2/src/include -D_GNU_SOURCE -c -o dbsize.o dbsize.c dbsize.c:1: postgres.h: No such file or directory dbsize.c:7:

Re: [GENERAL] Can't compile a contrib util: dbsize (probably simply though)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'd say you need to install the postgresql-devel package if you're on a rpm based system. On Thursday 10 June 2004 02:20 pm, Vitaly Belman wrote: Hello pgsql-general, When I am running make I get the following: gcc -O2 -fno-strict-aliasing

Re: [GENERAL] Can't compile a contrib util: dbsize (probably simply though)

On Fri, Jun 11, 2004 at 12:20:00AM +0300, Vitaly Belman wrote: Hello pgsql-general, When I am running make I get the following: gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I. -I~/postgresql-7.4.2/src/include -D_GNU_SOURCE -c -o dbsize.o

Re: [GENERAL] Can't compile a contrib util: dbsize (probably simply though)

Vitaly Belman [EMAIL PROTECTED] writes: gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I. -I~/postgresql-7.4.2/src/include -D_GNU_SOURCE -c -o dbsize.o dbsize.c dbsize.c:1: postgres.h: No such file or directory I don't understand why it can't find

Re: [GENERAL] Can't compile a contrib util: dbsize (probably simply though)

Hello Tom, Thanks, that worked. Regards, Vitaly Belman ICQ: 1912453 AIM: VitalyB1984 MSN: [EMAIL PROTECTED] Yahoo!: VitalyBe Friday, June 11, 2004, 12:55:53 AM, you wrote: TL Vitaly Belman [EMAIL PROTECTED] writes: gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes

[GENERAL] out of memory error

Hi, we are using Postgres with a J2EE application (JBoss) and get intermittent out of memory errors on the Postgres database. We are running on a fairly large Linux server (Dual 3GHz, 2GB Ram) with the following parameters: shared_buffers = 8192 sort_mem = 8192 effective_cache_size = 234881024

Re: [GENERAL] index with LIKE

Martijn van Oosterhout wrote: The classic issue is what encoding are the databases. Anything other than C and like won't use indexes. Unless you use text_pattern_ops. See http://www.postgresql.org/docs/7.4/static/indexes-opclass.html I think this needs to be in the faq.