Hi all,
I'm running postgresql 7.2.1 on a debian 3.0 machine and I want to do
some log rotation, but I'm having some problems. The configuration that
I'm using is:
In /etc/logrotate.d/postgres:
/var/log/postgres.log {
weekly
rotate 52
compress
delaycompress
not
On Thu, Nov 14, 2002 at 05:18:06PM -0500, Tom Lane wrote:
>
> The business about "you must vacuum at least every billion transactions"
> is a different issue. Either plain or full vacuum will satisfy that
> requirement.
Note, also, that it is _every_ table needs to be vacuumed in that
billion tr
running pgsql 7.2.1 on redhat7.3 SMP. installed a hacked glibc to fix the
mktime() timezone problem for dates < 1970
(http://rpms.arvin.dk/glibc/rh73/i686/)
three times now the backend process has unexpectedly quit. what happens is
the postmaster process and the stats processes disappear and only
This is just a guess, but try changing your script to do reload instead
of restart.
Robert Treat
On Wed, 2002-11-20 at 05:14, Luis Sousa wrote:
> Hi all,
>
> I'm running postgresql 7.2.1 on a debian 3.0 machine and I want to do
> some log rotation, but I'm having some problems. The configuratio
"Tim Lynch" <[EMAIL PROTECTED]> writes:
> running pgsql 7.2.1 on redhat7.3 SMP. installed a hacked glibc to fix the
> mktime() timezone problem for dates < 1970
> (http://rpms.arvin.dk/glibc/rh73/i686/)
> three times now the backend process has unexpectedly quit. what happens is
> the postmaster p
I said:
> "Tim Lynch" <[EMAIL PROTECTED]> writes:
>> i don't see a core file.
> Check that you are starting the postmaster with "ulimit -c unlimited";
> this is not the default on most Linuxen, so you may have to add that to
> the start script. Also note that the postmaster never does a chdir,
>
