On 1/20/08, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Marti Raudsepp wrote:
>>> However, as of PostgreSQL 8.3, postmaster requires that the number of
>>> buffers is at least (max_connections*2 + 6)
> It's sort of irrelevant IMHO, as any useful setting is orders
The following bug has been logged online:
Bug reference: 3888
Logged by: Marti Raudsepp
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC1
Operating system: Linux AMD64
Description:postmaster: misleading error message for illegal -B
values
Details:
When
even more against "common sense", but
at least it would be "correct" :)
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wed, Feb 22, 2012 at 23:40, Tom Lane wrote:
> Marti Raudsepp writes:
>> According to this model, evaluating SELECT clause fields for *all*
>> found rows is done in step 5, whereas LIMIT/OFFSET are only applied
>> later at step 9. So we're already bending the rules he
re composite types in tables, I think you're better off
using CREATE TYPE/ALTER TYPE.
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
curate picture of where the time is being spent.
Now, another question is whether to use text or binary output
functions. And where to account the time, since this happens outside
of the plan tree.
At the very least, I think this gotcha should be documented on the EXPLAIN page.
Regards,
Marti
-
erent query from there.
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
This has already been fixed. PostgreSQL 9.2beta says:
pg_restore: [archiver] input file appears to be a text format dump.
Please use psql.
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ifferent results at
different times, but you will always get consistent results to your
queries.
Regards,
Marti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
