Re: [BUGS] Postgres crash? could not write to log file: No space left on device

2013-06-26 Thread Greg Stark
On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane wrote: > (Though if it is, it's not apparent why such > failures would only be manifesting on the pg_xlog files and not for > anything else.) Well data files are only ever written to in 8k chunks. Maybe these errors are only occuring on >8k xlog records

Re: [BUGS] Postgres crash? could not write to log file: No space left on device

2013-06-26 Thread Andres Freund
On 2013-06-26 13:14:37 +0100, Greg Stark wrote: > On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane wrote: > > (Though if it is, it's not apparent why such > > failures would only be manifesting on the pg_xlog files and not for > > anything else.) > > Well data files are only ever written to in 8k chun

Re: [BUGS] Postgres crash? could not write to log file: No space left on device

2013-06-26 Thread Heikki Linnakangas
On 26.06.2013 15:21, Andres Freund wrote: On 2013-06-26 13:14:37 +0100, Greg Stark wrote: On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane wrote: (Though if it is, it's not apparent why such failures would only be manifesting on the pg_xlog files and not for anything else.) Well data files are o

Re: [BUGS] Postgres crash? could not write to log file: No space left on device

2013-06-26 Thread Andres Freund
On 2013-06-26 15:40:08 +0300, Heikki Linnakangas wrote: > On 26.06.2013 15:21, Andres Freund wrote: > >On 2013-06-26 13:14:37 +0100, Greg Stark wrote: > >>On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane wrote: > >>> (Though if it is, it's not apparent why such > >>>failures would only be manifesting o

Re: [BUGS] Postgres crash? could not write to log file: No spaceleft on device

2013-06-26 Thread Yuri Levinsky
Sorry for delay, the email somehow went into junk mails folder. I didn't compiled Postgres, we downloaded the already compiled version for SUN Solaris 10 64 bit. The same version is working fine on other installations. On this specific installation we got "buggy kernel" error during massive data

Re: [BUGS] Postgres crash? could not write to log file: No space left on device

2013-06-26 Thread Tom Lane
Heikki Linnakangas writes: > We've discussed retrying short writes before, and IIRC Tom has argued > that it shouldn't be necessary when writing to disk. Nevertheless, I > think we should retry in XLogWrite(). It can write much bigger chunks > than most write() calls, so there's more room for a

[BUGS] BUG #8255: encoding latin1

2013-06-26 Thread gabriel . ct
The following bug has been logged on the website: Bug reference: 8255 Logged by: gabriel Email address: gabriel...@santamonicace.com.br PostgreSQL version: 8.4.4 Operating system: windows xp Description: Good afternoon, I live in Brazil and I need to create a database

[BUGS] BUG #8256: query screen on pgAdmin is show blank

2013-06-26 Thread dmcmillan
The following bug has been logged on the website: Bug reference: 8256 Logged by: Dan Email address: dmcmil...@snapadvances.com PostgreSQL version: 9.2.4 Operating system: Mac OS version 10.8.4 Description: pgadmin 1.16.1 java version "1.7.0_21" Java(TM) SE Runtime E

Re: [BUGS] BUG #8256: query screen on pgAdmin is show blank

2013-06-26 Thread Ashesh Vashi
Try the View -> 'Default View' in the Query window. On Wed, Jun 26, 2013 at 8:55 PM, wrote: > The following bug has been logged on the website: > > Bug reference: 8256 > Logged by: Dan > Email address: dmcmil...@snapadvances.com > PostgreSQL version: 9.2.4 > Operating system:

[BUGS] BUG #8257: Multi-Core Restore fails when containing index comments

2013-06-26 Thread lalbin
The following bug has been logged on the website: Bug reference: 8257 Logged by: Lloyd Albin Email address: lal...@fhcrc.org PostgreSQL version: 9.2.4 Operating system: SUSE Linux (64-bit) Description: I have found the restore will fail when using pg_restore's -j opti

[BUGS] BUG #8238: duplicate of bug #6372 on panffs

2013-06-26 Thread Kristopher Kane
Sorry to replay in this way but I just joined the list based on a thread I found from a few days ago. I hit the panfs fsync problem this morning and it appears the same as what Jim Hughes is reporting. Initially thought it was SELinux (RHEL 6.4) but it persisted after I turned it off. Bug #6372 a