Valentin Bogdanov <[EMAIL PROTECTED]> writes:
> I run out of disk space on the box and had to delete some files and restart
> postgres. Ever since I have been getting the above message. PS shows this
> process:
> 9351 ?D 0:04 postgres: startup process
> Running an strace on this proc
"John Smith" <[EMAIL PROTECTED]> writes:
>> BTW, what's with the bizarre "Local time zone must be set--see zic
>> manual" where the timezone should be? Are you intentionally selecting
>> the "Factory" zone?
> I don't think I've put the correct timezone file in /etc/localtime so
> it is using som
Thanks for the quick reply Tom. I'll be updating my PG version to one
with a fix for bug #3245 so hopefully we won't see this anymore.
> BTW, what's with the bizarre "Local time zone must be set--see zic
> manual" where the timezone should be? Are you intentionally selecting
> the "Factory" zone
"John Smith" <[EMAIL PROTECTED]> writes:
> 2008-06-17 23:53:53.206 Local time zone must be set--see zic manual
> page PANIC: failed to re-find shared lock object
> 2008-06-17 23:53:53.207 Local time zone must be set--see zic manual
> page STATEMENT: commit prepared '148969' ;
> I believe this pa
Hi,
I hit an issue running PG 8.2.3 with the continuous archiving feature
where I was unable to recover from the backup. I was wondering if
this may be related to bug #3245?
These are the steps that occurred before I saw this problem:
1. Prepare transaction.
2. A base backup of the database w
Hi,
I run out of disk space on the box and had to delete some files and restart
postgres. Ever since I have been getting the above message. PS shows this
process:
9351 ?D 0:04 postgres: startup process
Running an strace on this process shows that it is trying to write 8K of zeros
