On Tue, Jul 22, 2008 at 5:54 PM, Achilleas Mantzios
<[EMAIL PROTECTED]> wrote:
> Στις Tuesday 22 July 2008 15:17:42 ο/η Rajesh Kumar Mallah έγραψε:
>> Hi,
>>
>> We want to log all SQLs that has been executed by using psql client.
>> we do not want to use .psql_history as it is distributed and may b
Achilleas Mantzios wrote:
Στις Tuesday 22 July 2008 15:17:42 ο/η Rajesh Kumar Mallah
ÎγÏ�αψε:
Hi,
We want to log all SQLs that has been executed by using psql
client. we do not want to use .psql_history as it is distributed
and may be deleted by users .
The original objective is tha
shared_buffers is in disk block size, typically 8K, at least that's what it is
on Linux platforms. shmmax is quite simply in bytes.
The default shared_buffer of a 1000 is quite conservative. A good starting
value is something like 15-25 percent of your main memory or so I am being
told. It real
Hi,
I'm trying to understand what the documentation means by bytes per increment,
what is the increment supposed to be bytes, MB, or Kb. I have my
shared_buffers set to 577 MB(4 instances) and I'm multiplying by 8400 bytes. I
would think I would want to keep everything in bytes and not mulitpl
Στις Tuesday 22 July 2008 15:17:42 ο/η Rajesh Kumar Mallah έγραψε:
> Hi,
>
> We want to log all SQLs that has been executed by using psql client.
> we do not want to use .psql_history as it is distributed and may be
> deleted by users .
>
> The original objective is that we should be able to know
Hi,
We want to log all SQLs that has been executed by using psql client.
we do not want to use .psql_history as it is distributed and may be
deleted by users .
The original objective is that we should be able to know what all hand made
SQLs have been executed in past (which can date back as lon
