On 12/22/2010 10:41 AM, Tom Lane wrote:
Adrian Klaver writes:
On 12/22/2010 09:03 AM, Tom Lane wrote:
I begin to wonder if the subdirectory $PGDATA/base/26468499 is there at
all?
Alright I am going to show my ignorance here, but why would it not be?
$PGDATA/base/1663/26468499
1663 is the
Adrian Klaver writes:
> On 12/22/2010 09:03 AM, Tom Lane wrote:
>> I begin to wonder if the subdirectory $PGDATA/base/26468499 is there at
>> all?
> Alright I am going to show my ignorance here, but why would it not be?
> $PGDATA/base/1663/26468499
1663 is the pg_default tablespace, which refers
On 12/22/2010 07:20 PM, Tom Lane wrote:
Sim Zacks writes:
FATAL: could not open relation 1663/26468499/1259: No such file or
directory
I begin to wonder if the subdirectory $PGDATA/base/26468499 is there at
all?
/var/lib/postgresql/8.2/data/base/26468499 does exist, and there are
1212 files
On 12/22/2010 07:20 PM, Tom Lane wrote:
Sim Zacks writes:
FATAL: could not open relation 1663/26468499/1259: No such file or
directory
I begin to wonder if the subdirectory $PGDATA/base/26468499 is there at
all?
/var/lib/postgresql/8.2/data/base/26468499 does exist, and there are
1212 files
Sim Zacks writes:
>>> FATAL: could not open relation 1663/26468499/1259: No such file or
>>> directory
>> I begin to wonder if the subdirectory $PGDATA/base/26468499 is there at
>> all?
> /var/lib/postgresql/8.2/data/base/26468499 does exist, and there are
> 1212 files in it, but so far all th
On 12/22/2010 09:03 AM, Tom Lane wrote:
Sim Zacks writes:
Our postgresql database stopped working with the error
ERROR: could not open relation 1663/26468499/26470404: No such file or
directory
Does the not connect also apply to starting postgres in single user mode?
Same error with single us
On 12/22/2010 07:03 PM, Tom Lane wrote:
Sim Zacks writes:
Our postgresql database stopped working with the error
ERROR: could not open relation 1663/26468499/26470404: No such file or
directory
Does the not connect also apply to starting postgres in single user mode?
Same error with single u
On 12/22/2010 06:45 PM, Adrian Klaver wrote:
On 12/22/2010 08:37 AM, Sim Zacks wrote:
On 12/22/2010 06:28 PM, Adrian Klaver wrote:
On 12/22/2010 07:59 AM, Sim Zacks wrote:
We are using postgresql 8.2.17 on Gentoo
Our postgresql database stopped working with the error
ERROR: could not open r
Sim Zacks writes:
> Our postgresql database stopped working with the error
> ERROR: could not open relation 1663/26468499/26470404: No such file or
> directory
>> Does the not connect also apply to starting postgres in single user mode?
> Same error with single user mode.
> postgres --single -D /v
On 12/22/2010 08:37 AM, Sim Zacks wrote:
On 12/22/2010 06:28 PM, Adrian Klaver wrote:
On 12/22/2010 07:59 AM, Sim Zacks wrote:
We are using postgresql 8.2.17 on Gentoo
Our postgresql database stopped working with the error
ERROR: could not open relation 1663/26468499/26470404: No such file or
On 12/22/2010 06:28 PM, Adrian Klaver wrote:
On 12/22/2010 07:59 AM, Sim Zacks wrote:
We are using postgresql 8.2.17 on Gentoo
Our postgresql database stopped working with the error
ERROR: could not open relation 1663/26468499/26470404: No such file or
directory
After one minute of these erro
On 12/22/2010 06:08 PM, Vick Khera wrote:
On Wed, Dec 22, 2010 at 10:59 AM, Sim Zacks wrote:
This is our production database and crashed at the end of the day. If
possible, I would really not like to lose a full days work by restoring
yesterdays backup.
So the errors in postgres started after
On 12/22/2010 07:59 AM, Sim Zacks wrote:
We are using postgresql 8.2.17 on Gentoo
Our postgresql database stopped working with the error
ERROR: could not open relation 1663/26468499/26470404: No such file or
directory
After one minute of these errors on every statement run we had what
looks lik
On Wed, Dec 22, 2010 at 10:59 AM, Sim Zacks wrote:
> This is our production database and crashed at the end of the day. If
> possible, I would really not like to lose a full days work by restoring
> yesterdays backup.
>
So the errors in postgres started after your server crashed? Sounds
like the
We are using postgresql 8.2.17 on Gentoo
Our postgresql database stopped working with the error
ERROR: could not open relation 1663/26468499/26470404: No such file or
directory
After one minute of these errors on every statement run we had what
looks like a memory failure:
Dec 22 16:37:44 lo
Alan Millington wrote:
> However, on looking at the matter again, I am now almost certain that
> I caused the problem myself. I have a Python function which (as a
> workaround to a problem which exists in Python 2.4, the version to
> which Postgres 8.1.4 is tied) executes a chdir. It appears that
On 19/08/2009 6:38 PM, Craig Ringer wrote:
Got a virus scanner installed? If so, remove it (do not just disable it) and
see if you can reproduce the problem. Ditto anti-spyware software.
You should also `chkdsk' your file system(s) and use a SMART diagnostic tool to
test your hard disk (assum
On Fri, 2009-08-21 at 11:30 +1000, Yaroslav Tykhiy wrote:
> Hi there,
>
> On 19/08/2009, at 8:38 PM, Craig Ringer wrote:
> > You should also `chkdsk' your file system(s) and use a SMART
> > diagnostic tool to test your hard disk (assuming it's a single ATA
> > disk).
>
> By the way, `chkdsk'
On 21/08/2009, at 12:40 PM, Seth Gordon wrote:
Yaroslav Tykhiy wrote:
By the way, `chkdsk' in Windows or `fsck' in Unix can, in a way, be
a _source_ of file loss if the file metadata got damaged badly,
e.g., by a system crash, and the file node has to be cleared. So
I've always been curio
Yaroslav Tykhiy wrote:
By the way, `chkdsk' in Windows or `fsck' in Unix can, in a way, be a
_source_ of file loss if the file metadata got damaged badly, e.g., by a
system crash, and the file node has to be cleared. So I've always been
curious if there is a way to retrieve surviving records f
Hi there,
On 19/08/2009, at 8:38 PM, Craig Ringer wrote:
On 19/08/2009 6:26 PM, Alan Millington wrote:
2009-08-19 03:06:45 ERROR: could not read block 0 of relation
1663/52752/52896: No such file or directory
Clearly something is amiss, but I don't know what. I should be
grateful
for any
On Wed, Aug 19, 2009 at 4:26 AM, Alan
Millington wrote:
> I am running Postgres 8.1.4 on Windows XP Professional Service Pack 3.
In addition to the very helpful advice Craig provided, you also need
to look at upgrading your pgsql install. 8.1 is no longer supported
on windows due to issues in it
On 19/08/2009 6:26 PM, Alan Millington wrote:
2009-08-19 03:06:45 ERROR: could not read block 0 of relation
1663/52752/52896: No such file or directory
Clearly something is amiss, but I don't know what. I should be grateful
for any suggestions as to what I should check.
Got a virus scanner
I am running Postgres 8.1.4 on Windows XP Professional Service Pack 3.
Yesterday when attempting to select from one particular database I repeatedly
encountered errors such as the following:
2009-08-18 10:49:54 ERROR: could not open relation 1663/51796/1247: No such
file or directory
2009-08
ministering and explaining Postgres?
Many thanks
Jaime
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Monday, August 07, 2006 9:58 AM
To: Harald Armin Massa
Cc: pgsql-general
Subject: Re: [GENERAL] could not open relation - why?
"Harald
> Oh, I assumed you had reason to think that the error message came from> autovacuum. It could easily have been the same situation except two> unrelated processes.Surely my mistake in error reporting. Just cut out the "surrounding lines" from the log; like in contextual diff :(
> What indeed happe
"Harald Armin Massa" <[EMAIL PROTECTED]> writes:
>> The easiest explanation is that someone dropped a table just as
>> autovacuum was trying to open it.
> I am not quite sure that "autovacuum" was trying to open, as some user
> reported the same error on his system ( and he is definitely not mr.
>
> 2006-08-07 13:20:27 LOG: autovacuum: processing database "template1"
> 2006-08-07 13:20:47 ERROR: could not open relation with OID 311438> 2006-08-07 13:21:52 LOG: autovacuum: processing database "postgres"The easiest explanation is that someone dropped a table just as
autovacuum was trying to
"Harald Armin Massa" <[EMAIL PROTECTED]> writes:
> within my log there is the following snippet:
> 2006-08-07 13:20:27 LOG: autovacuum: processing database "template1"
> 2006-08-07 13:20:47 ERROR: could not open relation with OID 311438
> 2006-08-07 13:21:52 LOG: autovacuum: processing database
Hello,within my log there is the following snippet:2006-08-07 13:20:27 LOG: autovacuum: processing database "template1"2006-08-07 13:20:47 ERROR: could not open relation with OID 3114382006-08-07 13:21:52 LOG: autovacuum: processing database "postgres"
now there are a number of possibilites, why
On 1/6/06, Sebastjan Trepca <[EMAIL PROTECTED]> wrote:
> Hi,
>
> postgres just started to report this error yesterday when I ran a user
> function which deletes rows in a lot of tables.
> I get an error:
>
> "Could not open relation with OID 18789"
>
> The function looks like this:
>
> CREATE OR RE
Hi,postgres just started to report this error yesterday when I ran a user function which deletes rows in a lot of tables.I get an error:"Could not open relation with OID 18789"The function looks like this:
CREATE OR REPLACE FUNCTION delete_photo(int8) RETURNS bool AS$BODY$DECLAREgid RECORD;photo R
Chris <[EMAIL PROTECTED]> writes:
> This is Postgresql 8 RC 1 on freebsd 5.3.
> I changed the type of a column from varchar(128) to varchar(256), and
> right after that I got the following messages when doing inserts on
> the table in question.
> <41e0e2c3.fd54>ERROR: SMgrRelation hashtable corr
This is Postgresql 8 RC 1 on freebsd 5.3.
I changed the type of a column from varchar(128) to varchar(256), and
right after that I got the following messages when doing inserts on
the table in question.
<41e0e2c3.fd54>ERROR: SMgrRelation hashtable corrupted
<41e0e2c3.fd54>STATEMENT: commit
<4
Hi, everybody!
I already solved it. Thank you.
First of, I forgot to mention the version(), so FYI, 7.4.1.
I followed Tom's advice in
http://archives.postgresql.org/pgsql-general/2004-03/msg01073.php
I shut down the PG instance.
postgres -D $PG_DATA -O -P $DBNAME
=# REINDEX DATABASE tbc_gamma
35 matches
Mail list logo
