On 8/8/06, Thomas F. O'Connell <[EMAIL PROTECTED]> wrote:
On Aug 8, 2006, at 1:10 PM, Merlin Moncure wrote:
> On 8/8/06, Thomas F. O'Connell <[EMAIL PROTECTED]> wrote:
>> On Aug 3, 2006, at 1:26 PM, Merlin Moncure wrote:
>> > if have super high write volumes, consider writing your insert
>> cal
On Aug 8, 2006, at 1:10 PM, Merlin Moncure wrote:
On 8/8/06, Thomas F. O'Connell <[EMAIL PROTECTED]> wrote:
On Aug 3, 2006, at 1:26 PM, Merlin Moncure wrote:
> if have super high write volumes, consider writing your insert
call in
> C. prepare your statement, and use the parameterized
> ver
On 8/8/06, Thomas F. O'Connell <[EMAIL PROTECTED]> wrote:
On Aug 3, 2006, at 1:26 PM, Merlin Moncure wrote:
> if have super high write volumes, consider writing your insert call in
> C. prepare your statement, and use the parameterized
> versionExecPrepared(...).
Can you point to a good exam
On Aug 3, 2006, at 1:26 PM, Merlin Moncure wrote:
On 8/2/06, Thomas F. O'Connell <[EMAIL PROTECTED]> wrote:
I'm working on a postgres instance (8.1.2 running on Solaris 10)
where the
data directory (including WAL) is being mounted on tmpfs. Based on
this, and
with knowledge that fsync is di
On 8/2/06, Thomas F. O'Connell <[EMAIL PROTECTED]> wrote:
I'm working on a postgres instance (8.1.2 running on Solaris 10) where the
data directory (including WAL) is being mounted on tmpfs. Based on this, and
with knowledge that fsync is disabled, I'm operating under the assumption
that recovera
