We figured that out. We were afraid that there was corrupt data due the
counter overflow so we reverted to a backup right before the overflow. We
submitted a bug this morning (bug #12990) to the Postgres bugs mailing list
which has more information and questions.
On Mon, Apr 6, 2015 at 2:17 PM, Al
Pweaver (Paul Weaver) wrote:
> We started getting the following error on some transactions on our database
> (when against particular rows run against the table).
>
>
> PGError: ERROR: could not access status of transaction 283479860 DETAIL:
> Could not open file "pg_multixact/members/4D6D": No s
We started getting the following error on some transactions on our database
(when against particular rows run against the table).
PGError: ERROR: could not access status of transaction 283479860 DETAIL:
Could not open file "pg_multixact/members/4D6D": No such file or directory.
We don't know wha
On Tue, 21 Jul 2009, Merlin Moncure wrote:
One way to suppress this error, but not fix the underlying corruption,
is to generate clog files that the database thinks should be there.
Make a 256k file filled with 0x55 and put it where the database is
expecting.
Here's a list of past messages on
On Tue, 21 Jul 2009 15:32:07 -0400
Merlin Moncure wrote:
> 2009/7/21 Bjørn T Johansen :
> > I have had som problem with my filesystem and now I get these error
> > messsages when trying to access my database..:
> >
> > ERROR: could not access status of transaction 2495690984
> > Could not open
2009/7/21 Bjørn T Johansen :
> I have had som problem with my filesystem and now I get these error messsages
> when trying to access my database..:
>
> ERROR: could not access status of transaction 2495690984
> Could not open file "pg_clog/094C": No such file or directory.
got backups?
One way
I have had some problem with my filesystem and now I get these error messsages
when trying to access my database..:
ERROR: could not access status of transaction 2495690984
Could not open file "pg_clog/094C": No such file or directory.
Is there a way to fix this or do I have to find a backup?
I have had som problem with my filesystem and now I get these error messsages
when trying to access my database..:
ERROR: could not access status of transaction 2495690984
Could not open file "pg_clog/094C": No such file or directory.
Is there a way to fix this or do I have to find a backup?
On 10/19/07, Ralph Smith <[EMAIL PROTECTED]> wrote:
> > On 10/19/07, Ralph Smith <[EMAIL PROTECTED]> wrote:
> >> Thank you Scott!
> >>
> >> I'm away from my desk and will dive back into it.
> >> Fortunately I have two machines, each w/ 7.4 & 8.2 on them. New
> >> installs on Ubuntu 7.4.
> >>
> >>
On 10/19/07, Ralph Smith <[EMAIL PROTECTED]> wrote:
Thank you Scott!
I'm away from my desk and will dive back into it.
Fortunately I have two machines, each w/ 7.4 & 8.2 on them. New
installs on Ubuntu 7.4.
As to why I had 'no role or database' errors yesterday, am I right
that it was either:
On 10/19/07, Ralph Smith <[EMAIL PROTECTED]> wrote:
> Thank you Scott!
>
> I'm away from my desk and will dive back into it.
> Fortunately I have two machines, each w/ 7.4 & 8.2 on them. New
> installs on Ubuntu 7.4.
>
> As to why I had 'no role or database' errors yesterday, am I right
> that it
Thank you Scott!
I'm away from my desk and will dive back into it.
Fortunately I have two machines, each w/ 7.4 & 8.2 on them. New
installs on Ubuntu 7.4.
As to why I had 'no role or database' errors yesterday, am I right
that it was either:
A) I accidentally did a pg_dump when I thought
On 10/19/07, Ralph Smith <[EMAIL PROTECTED]> wrote:
> I'm using 7.4 in preparation for an overdue upgrade.
>
> Yesterday I posted 2 questions that were ignored, so I'll try a third now.
>
> When doing a query I get same error as below, which are the results of
> vacuumdb.
>
> vacuumdb: vacuuming o
I'm using 7.4 in preparation for an overdue upgrade.
Yesterday I posted 2 questions that were ignored, so I'll try a third
now.
When doing a query I get same error as below, which are the results
of vacuumdb.
vacuumdb: vacuuming of database "airburst" failed: ERROR: could not
access st
"Stuart Grimshaw" <[EMAIL PROTECTED]> writes:
> On 12/23/06, Stuart Grimshaw <[EMAIL PROTECTED]> wrote:
>> berble=# select * from headlines ;
>> ERROR: could not access status of transaction 1668180339
>> DETAIL: could not open file "pg_clog/0636": No such file or directory
>>
>> Using Postgres
On 12/23/06, Stuart Grimshaw <[EMAIL PROTECTED]> wrote:
berble=# select * from headlines ;
ERROR: could not access status of transaction 1668180339
DETAIL: could not open file "pg_clog/0636": No such file or directory
Using Postgres 8.1.5 from Debian unstable, I got the above error, and
I have
berble=# select * from headlines ;
ERROR: could not access status of transaction 1668180339
DETAIL: could not open file "pg_clog/0636": No such file or directory
Using Postgres 8.1.5 from Debian unstable, I got the above error, and
I have no idea what it means?
--
-S
Sports Photography in Sou
I recently saw this in some postgres logs:
ERROR: could not access status of transaction ...
DETAIL: could not open file "pg_clog/...": No such file or directory
STATEMENT: COPY ...
The copy command was issued amongst a number of other queries from an
application layer at the same time as a
On Mon, 2004-11-29 at 12:57 -0500, Tom Lane wrote:
> Scott Cain <[EMAIL PROTECTED]> writes:
> > After dropping a database, recreating it and trying to add a table to
> > it, I am getting this message:
>
> > ERROR: could not access status of transaction 210
> > DETAIL: could not open file "/opt/p
Scott Cain <[EMAIL PROTECTED]> writes:
> After dropping a database, recreating it and trying to add a table to
> it, I am getting this message:
> ERROR: could not access status of transaction 210
> DETAIL: could not open file "/opt/postgres/data/pg_clog/": No such file
> or directory
> The
Hello,
After dropping a database, recreating it and trying to add a table to
it, I am getting this message:
NOTICE: CREATE TABLE will create implicit sequence
"tableinfo_tableinfo_id_seq" for "serial" column "tableinfo.tableinfo_id"
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
21 matches
Mail list logo
