On 1st May, I saw this message in my postgres log:
May 2 06:52:02 db10 postgres[3590]: [29829-1] 2011-05-02 06:52:02 SGT
ERROR: could not access status of transaction 1573786613
May 2 06:52:02 db10 postgres[3590]: [29829-2] 2011-05-02 06:52:02 SGT
DETAIL: Could not open file "pg_clog/05DC":
Tomasz Chmielewski wrote:
> On 1st May, I saw this message in my postgres log:
>
> May 2 06:52:02 db10 postgres[3590]: [29829-1] 2011-05-02 06:52:02
> SGT ERROR: could not access status of transaction 1573786613
> May 2 06:52:02 db10 postgres[3590]: [29829-2] 2011-05-02 06:52:02
> SGT DETAIL
On 04.05.2011 20:14, Kevin Grittner wrote:
> Tomasz Chmielewski wrote:
>
>> On 1st May, I saw this message in my postgres log:
>>
>> May 2 06:52:02 db10 postgres[3590]: [29829-1] 2011-05-02 06:52:02
>> SGT ERROR: could not access status of transaction 1573786613
>> May 2 06:52:02 db10 postgres
Tomasz Chmielewski wrote:
> This repeated many times:
>
> /var/log/postgresql/postgresql_log.1:May 3 18:24:49 db10
> postgres[21363]: [26999-1] 2011-05-03 18:24:49 SGT ERROR: could
> not access status of transaction 1573786613
> /var/log/postgresql/postgresql_log.1-May 3 18:24:49 db10
< post
On Wed, May 4, 2011 at 12:37 PM, Tomasz Chmielewski wrote:
> /var/log/postgresql/postgresql_log.1:May 3 18:24:49 db10 postgres[21363]:
> [26999-1] 2011-05-03 18:24:49 SGT ERROR: could not access status of
> transaction 1573786613
> /var/log/postgresql/postgresql_log.1-May 3 18:24:49 db10 post
On 04.05.2011 21:50, Scott Marlowe wrote:
> Then another pg_clog file disappeared.
>
> Is it possible there's some rogue process deleting files in pg_clog
> somehow?
I don't think.
> Have you run an fsck on this drive to make sure it's not got
> any file system errors?
Also, don't think there
On 04.05.2011 22:13, Tomasz Chmielewski wrote:
> On 04.05.2011 21:50, Scott Marlowe wrote:
>
>> Then another pg_clog file disappeared.
OK, I have:
bookstor=# SELECT * FROM core_wot_seq;
sequence_name | last_value | increment_by | max_value | min_value
| cache_value | log_cnt | is_
On 04.05.2011 22:27, Tomasz Chmielewski wrote:
Then another pg_clog file disappeared.
OK, I have:
bookstor=# SELECT * FROM core_wot_seq;
sequence_name | last_value | increment_by | max_value |
min_value | cache_value | log_cnt | is_cycled | is_called
--+---
On 06.05.2011 10:42, Tomasz Chmielewski wrote:
On 04.05.2011 22:27, Tomasz Chmielewski wrote:
Then another pg_clog file disappeared.
OK, I have:
bookstor=# SELECT * FROM core_wot_seq;
sequence_name | last_value | increment_by | max_value | min_value |
cache_value | log_cnt | is_cycled | is_c
On 07.05.2011 23:19, Tomasz Chmielewski wrote:
On 06.05.2011 10:42, Tomasz Chmielewski wrote:
bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE;
ERROR: could not access status of transaction 1573786613
DETAIL: Could not open file "pg_clog/05DC": No such file or directory.
How do I best recover
Tomasz Chmielewski writes:
> bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE;
Um ... why are you doing that on a sequence?
> ERROR: could not access status of transaction 1573786613
> DETAIL: Could not open file "pg_clog/05DC": No such file or directory.
This doesn't surprise me too much, beca
On 31.05.2011 05:16, Tom Lane wrote:
> Tomasz Chmielewski writes:
>> bookstor=# SELECT 1 FROM core_wot_seq FOR UPDATE;
>
> Um ... why are you doing that on a sequence?
>
>> ERROR: could not access status of transaction 1573786613
>> DETAIL: Could not open file "pg_clog/05DC": No such file or dir
12 matches
Mail list logo
