:[EMAIL PROTECTED]
Sent: Tuesday, January 16, 2007 19:12
To: Jan van der Weijde; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Performance with very large tables
On Tue, Jan 16, 2007 at 12:06:38 -0600,
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>
> Depending on exactly what
Unfortunately a large C program has already been written.. But if a
function like PQsetFetchSize() was available in libpq, that would also
solve the problem.
From: Shoaib Mir [mailto:[EMAIL PROTECTED]
Sent: Monday, January 15, 2007 13:49
To: Jan van der Weijde
make much difference.
I would expect that the default behavior of PostgreSQL should be such
that without LIMIT, a SELECT returns records immediately.
Thank you,
Jan
-Original Message-
From: Alban Hertroys [mailto:[EMAIL PROTECTED]
Sent: Monday, January 15, 2007 12:49
To: Jan van der Weijde
about 25 seconds before the select returned the
first record. I tried it both interactively with pgAdmin and with a
C-application using a cursor (with hold). Both took about the same time.
Thanks,
Jan van der Weijde
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent
from ideal I think.
Does anyone have a suggestion for this problem ? Is there for instance
an alternative to LIMIT/OFFSET so that SELECT on large tables has a good
performance ?
Thank you for your help
Jan van der Weijde
Hi
All,
I have an issue with
timestamp with time zone I don't understand.
When I insert a time
stamp value '1903-08-07 00:00:00+02' into a table and next select it again using
psql I get '1903-08-06 22:19:32+00:19'.
I'm located in The
Netherlands and before 1940 there was a so called Am
