Lately my database crashed and I’ve
had some strangeness following.
I found that some tables would have two
distinct rows with identical primary key.
Now, VACUUM complains thusly
WARNING: index
"pg_statistic_relid_att_index" contains 2984 row versions, but table
contains 2983 row
le
complexity, and potentially uneccessary overhead to the application.
Something to consider (although admittedly it is arguably a weak
consideration in some circumstances) is the extra space, indexes, and
other factors such as additional time for backup routines (and
restoration) the extra table crea
--
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alban Hertroys
Sent: Monday, August 28, 2006 4:57 AM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] speeding up big query lookup
Silvela, Jaime (Exchange) wrote:
> The obvoious way
I had this problem a few weeks ago.
What I did was isolate it into an
individual row that was causing the problem, then going over the fields one by
one, till I located the free text field that was responsible.
Then I repopulated it with the value in
the latest backup I could find.
I was
This is a question on speeding up some type of queries.
I have a very big table that catalogs measurements of some objects over
time. Measurements can be of several (~10) types. It keeps the
observation date in a field, and indicates the type of measurement in
another field.
I often need to get t
sday, August 24, 2006 9:06 AM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general
Subject: Re: [GENERAL] Can't open Postgres at all!!!
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes:
> I just came back this morning after doing a REINDEX of pg_class
> Nothing is
Excuse my ignorance, how do I do that. Linux env setting? Is it a
command line option for Postmaster?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 24, 2006 9:06 AM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general
Subject: Re: [GENERAL] Can't
s Tom, lately I have seen a couple of small issues that may
indicate
hardware flakiness. Postgres version is 8.1.2 on linux.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 7:43 PM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general
Subject: Re: [GE
EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 7:10 PM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general
Subject: Re: [GENERAL] CASCADING could not open relation with OID
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes:
> I get
> Oid: 16896
> Relname: bb_master
Hm
I get
Oid: 16896
Relname: bb_master
Relnamespace: 16392
Reltype: 16897
...
Reltablespace: 0
Relpages: 0
Reltuples: 0
...
Relkind: r
...
Thanks
Jaime
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 6:54 PM
To: Silvela, Jaime (Exchange)
Cc
I get values frin the first statement but not from the second.
After setting indexscan to off, still the same thing.
Should this setting be off in general?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 6:15 PM
To: Silvela, Jaime (Exchange
aime
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 5:20 PM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general
Subject: Re: [GENERAL] CASCADING could not open relation with OID
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]
I’ve seen that some
other people have had ERROR could not open relation with OID ###
The suggested cause was
somebody trying to drop a table in the middle of VACUUM.
In my case, the error seems
to be spreading. Initially it affected only one table in a staging area that
would get
I had the same problem reported by VACUUM, and I traced it down to an
individual table, for which SELECT * would return the exact same
message.
As far as I know, no process or person has tried to drop the table at
any point. Luckily it's a table populated by an importer every day, and
I have a cop
I think this cropped up before, but can’t find it.
I’ve run into a problem in which I get “Missing
chunk number 0 for toast value 642223827”
I’ve tried reindexing the table and restarting the
server, but the problem persists.
I located an archive
“hunt down the damaged main row
ar(20),
msa varchar(3),
"year" int4,
"month" int2,
freq varchar(2),
geog varchar(6)
)
Thanks
Jaime
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 26, 2006 5:05 PM
To: Alvaro Herrera
Cc: Silvela, Jaime (Exchange); pgsql-gen
PM
To: Silvela, Jaime (Exchange)
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] copy losing information
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes:
> I've started to notice missing info sometimes. I'll truncate the
table,
> read from the file, and
This is the first time I post to the list. I’ve done a
brief search and didn’t find my issue treated already, so here it goes. Apologies
if this has been reported before.
I have a pretty big file, around 2 million rows, in
tab-separated format, with 4 columns, that I read into a table i
18 matches
Mail list logo
