I'm motivated to contribute a patch for that.
I would prefer to make tuple_fraction for cursors configurable as GUC
parameter cursor_tuple_fraction.
Do you agree with that?
Regards,
Robert
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 02. April 2008 00:24
T
Greg Smith wrote:
"After a write() to a regular file has successfully returned, any
successful read() from each byte position in the file that was
modified by that write() will return the data that was written by the
write()...a similar requirement applies to multiple write operations
to the s
Stephen Denne wrote:
A third option is to update, if not found, insert.
I find myself having to do this in Sybase, but it sucks because there's
a race - if there's no row updated then there's no lock and you race
another thread doing the same thing. So you grab a row lock on a
sacrificial ro
Am Mittwoch, den 02.04.2008, 20:10 +0100 schrieb James Mansion:
> It strikes me as odd that fsync_writethrough isn't the most preferred
> option where
> it is implemented. The postgres approach of *requiring* that there be no
> cache
> below the OS is problematic, especially since the battery ba
Andreas Kostyrka wrote:
takes over. The thing you worry about is if all data has made it to the
replication servers, not if some data might get lost in the hardware
cache of a controller. (Actually, talk to your local computer forensics
guru, there are a number of way to keep the current to elect
On Wed, 2 Apr 2008, James Mansion wrote:
But amusingly, PostgreSQL doesn't even support Solaris's direct I/O
method right now unless you override the filesystem mounting options,
so you end up needing to split it out and hack at that level
regardless.
Indeed that's a shame. Why doesn't it use
On Wed, 2 Apr 2008, James Mansion wrote:
I'm well aware that there are battery-backed caches that can be detached
from controllers and moved. But you'd better make darn sure you move
all the drives and plug them in in exactly the right order and make sure
they all spin up OK with the replaced
On Wed, Apr 2, 2008 at 1:16 AM, James Mansion
<[EMAIL PROTECTED]> wrote:
> Tried harder to find info on the write cycles: found som CFs that claim
> 2million
> cycles, and found the Mtron SSDs which claim to have very advanced wear
> levelling and a suitably long lifetime as a result even with a
What can be set as max of postgreSQL shared_buffers and work_mem
2008-04-03
bitaoxiao
Greg Smith wrote:
You turn on direct I/O differently under Solaris then everywhere else,
and nobody has bothered to write the patch (trivial) and OS-specific
code to turn it on only when appropriate (slightly tricker) to handle
this case. There's not a lot of pressure on PostgreSQL to handle th
10 matches
Mail list logo
