t; > FreeBSD 10.3, we've started seeing those after upgrading from postgres
> > 9.1.18 on more than one system, so hardware (e.g. RAM issues) are very
> > unlikely. I suspect that postgres is at fault, however I am also curious
> > how could it be that kernel is no
On Mon, Jul 04, 2016 at 10:26:25PM -0700, Maxim Sobolev wrote:
> Hi all, investigating some random postgresql-9.1.21 server crashes on
> FreeBSD 10.3, we've started seeing those after upgrading from postgres
> 9.1.18 on more than one system, so hardware (e.g. RAM issues) are very
Hi all, investigating some random postgresql-9.1.21 server crashes on
FreeBSD 10.3, we've started seeing those after upgrading from postgres
9.1.18 on more than one system, so hardware (e.g. RAM issues) are very
unlikely. I suspect that postgres is at fault, however I am also curious
how cou
I'm seeing a condition on FreeBSD 9.1 (built October 24th) where I/O seems to
hang on any local zpools after several hours of hosting a large-ish Postgres
database. The database occupies about 14TB of a 38TB zpool with a single SSD
ZIL. The OS is on a ZFS boot disk. The system also has 24
if the perms really need to be 600 i would do this (anyway i dont
see a reason why other users should access /root)
chmod 700 /root
chmod 600 /root/.pgpass
also check the ownership of these files
--
>
> > I'm trying to write a backup script for postgres and us a crontab on
> I'm trying to write a backup script for postgres and us a crontab on it.
> In the manual it says for pg_dumpall make $HOME/.pgpass so it won't ask
> for a password.
Do you use the correct .pgpass format?
It must be like that:
hostname:port:database:username:password
> Now
I'm trying to write a backup script for postgres and us a crontab on it.
In the manual it says for pg_dumpall make $HOME/.pgpass so it won't ask
for a password.
Now I made the .pgpass in root's homedir (i wanted to use root's
crontab) paste the password in it, chmod 400 it .
On Fri, 12 Jul 2002, Vivek Khera wrote:
> > "IS" == Igor Sysoev <[EMAIL PROTECTED]> writes:
>
> >> The kernel config has SHMMAX and SHMMAXPGS.
>
> IS> Sorry, I'd meant "SHMMAXPGS is sysctl kern.ipc.shmall".
>
> Actually, SHMMAXPGS * 4096 == kern.ipc.shmmax
>
> so if you set SHMMAXPGS to
On Wed, 10 Jul 2002, Vivek Khera wrote:
> I have a dual cpu box with 2GB RAM dedicated to running Postgres.
> Last week, I upgraded FreeBSD from 4.4-STABLE to 4.6-RELEASE-p1. When
> I went to restart postgres, it complained that it could not allocate
> the shared memory segment.
This is just a heads up to people who use INN/Diablo (USENET news
feed systems), or postgres/mysql (database systems) in heavily
loaded environment. I recently MFC'd a major fix to a performance issue
that was accidently introduced in late 2000. A security fix ha
10 matches
Mail list logo