Skip site navigation (1) Skip section navigation (2)

Re: does wal archiving block the current client connection?

From: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: does wal archiving block the current client connection?
Date: 2006-05-23 04:10:54
Message-ID: Pine.LNX.4.64.0605222103510.7012@discord.home.frostconsultingllc.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
On Tue, 23 May 2006, Tom Lane wrote:

> I'm still thinking that the simplest explanation is that $PGDATA/pg_clog/
> is on the NAS device.  Please double-check the file locations.

I know that seems like an excellent candidate, but it really isn't, I swear. 
In fact, you almost had me convinced the last time you asked me to check.. I 
thought some helpful admin had moved something, but no:

postgres  9194  0.0  0.4 486568 16464 ?      S    May16   0:11 
/usr/local/pgsql/bin/postmaster -p 5432 -D /usr/local/pgsql/data

db3:~/data $ pwd
/usr/local/pgsql/data

db3:~/data $ ls -l
total 64
-rw-------  1 postgres postgres     4 Feb 13 20:13 PG_VERSION
drwx------  6 postgres postgres  4096 Feb 13 21:00 base
drwx------  2 postgres postgres  4096 May 22 21:03 global
drwx------  2 postgres postgres  4096 May 22 17:45 pg_clog
-rw-------  1 postgres postgres  3575 Feb 13 20:13 pg_hba.conf
-rw-------  1 postgres postgres  1460 Feb 13 20:13 pg_ident.conf
drwx------  4 postgres postgres  4096 Feb 13 20:13 pg_multixact
drwx------  2 postgres postgres  4096 May 22 20:45 pg_subtrans
drwx------  2 postgres postgres  4096 Feb 13 20:13 pg_tblspc
drwx------  2 postgres postgres  4096 Feb 13 20:13 pg_twophase
lrwxrwxrwx  1 postgres postgres     9 Feb 13 22:10 pg_xlog -> /pg_xlog/
-rw-------  1 postgres postgres 13688 May 16 17:50 postgresql.conf
-rw-------  1 postgres postgres    63 May 16 17:54 postmaster.opts
-rw-------  1 postgres postgres    47 May 16 17:54 postmaster.pid

db3:~/data $ mount
/dev/sda2 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/sdb1 on /usr/local/pgsql type ext3 (rw,data=writeback)
/dev/sda5 on /var type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
//10.1.1.28/pgbackup on /mnt/pgbackup type cifs (rw,mand,noexec,nosuid,nodev)

So, no..I wish it was that easy. :-/

If you have any other suggestions or inspirations, I'm all ears!

-- 
Jeff Frost, Owner 	<jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954

In response to

pgsql-hackers by date

Next:From: Thomas HallgrenDate: 2006-05-23 07:03:36
Subject: API changes in patch release
Previous:From: Tom LaneDate: 2006-05-23 04:02:25
Subject: Re: does wal archiving block the current client connection?

pgsql-admin by date

Next:From: Meyer MarcoDate: 2006-05-23 06:50:45
Subject: How to mesure transaction rate in Postgres
Previous:From: Tom LaneDate: 2006-05-23 04:02:25
Subject: Re: does wal archiving block the current client connection?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group