Simon Riggs wrote:
The objections to applying this patch originally were:
1. it changes on-disk format (we've done this, so argument is void)
I'm little bit confused when we introduce new page layout version? I
expect that new version become with changes with pageheader, tuple
header or
I have two types of tables, for sake of argument lets call it these:
1) product 10,000,000 rows
2) product_activity 1,000,000,000 rows
90% of the type the product table is accessed by product_id, 80% of
the time that product id would be in the last 1,000,000 rows of the
table
Zdenek Kotala [EMAIL PROTECTED] writes:
I'm little bit confused when we introduce new page layout version? I
expect that new version become with changes with pageheader, tuple
header or data encoding (varlen/TOAST ...). But in case when there is
new data type internal implementation, there
The maximum for bgwriter_delay is currently 10 seconds. That's a long
time, and in fact if you set it to a value greater than 1 s, the sleep
is split into 1 s intervals with a call to AbsorbFsyncRequests in
between them.
Is there a use case for a setting 1 s? We could simplify that logic a
Tim,
I have two types of tables, for sake of argument lets call it these:
1) product 10,000,000 rows
2) product_activity 1,000,000,000 rows
pgsql-performance is the correct list for your question. Please re-post it
there. -hackers is for PostgreSQL development.
--
Josh
Jim,
I know there's issues with using ident sameuser via TCP, but what
about for filesystem socket connections?
Not all OSes support ident ... Solaris and OpenBSD for two, don't, because
they see ident as insecure.
We switched the default to trust localhost only after many, many complaints
On Mon, 2007-06-18 at 20:02 +0200, Peter Eisentraut wrote:
Am Montag, 18. Juni 2007 19:03 schrieb Tom Lane:
In time-related contexts (eg ISO 8601) I'd expect just h m and s.
ISO 8601 appears to use a slightly different syntax for writing timespans. I
would not object if anyone added
On Tue, 2007-06-19 at 15:53 +0100, Heikki Linnakangas wrote:
The maximum for bgwriter_delay is currently 10 seconds. That's a long
time, and in fact if you set it to a value greater than 1 s, the sleep
is split into 1 s intervals with a call to AbsorbFsyncRequests in
between them.
Is
On Fri, 2007-06-15 at 15:01 -0400, Stephen Frost wrote:
But we'd only get 31 bits of room to encode that into. I'm not sure if
that's enough. :( At the moment there's three columns we're talking
about in the side-table:
SRID (integer)
TYPE (varchar(30))
DIMENSIONS (integer)
Now, the
Simon Riggs wrote:
On Tue, 2007-06-19 at 15:53 +0100, Heikki Linnakangas wrote:
The maximum for bgwriter_delay is currently 10 seconds. That's a long
time, and in fact if you set it to a value greater than 1 s, the sleep
is split into 1 s intervals with a call to AbsorbFsyncRequests in
I'm seeing some applications where it appears that there would be
value in introducing asynchronous messaging, ala message queueing.
http://en.wikipedia.org/wiki/Message_queue
The granddaddy of message queuing systems is IBM's MQ-Series, and I
don't see particular value in replicating its
On Jun 19, 2007, at 2:45 PM, Chris Browne wrote:
I'm seeing some applications where it appears that there would be
value in introducing asynchronous messaging, ala message queueing.
http://en.wikipedia.org/wiki/Message_queue
Me too.
My bias would be to have something that can basically run
Simon Riggs wrote:
On Mon, 2007-06-18 at 20:02 +0200, Peter Eisentraut wrote:
Am Montag, 18. Juni 2007 19:03 schrieb Tom Lane:
In time-related contexts (eg ISO 8601) I'd expect just h m and s.
ISO 8601 appears to use a slightly different syntax for writing timespans.
I
would not
13 matches
Mail list logo
