strange error
I don't know if this mailing list is the appropriate ML, but:
I think that in postgresql 6.3.2 there is a little bug.
I have a table. I exec:
alter table my_table add column mycolumn mytype\g
now if I make a select on this new column I get this error
ERROR: RestrictionClauseSelectivity: bad value 2.350645
Otherwise, if I drop the my_table and recreate my_table with the new
column all
is work. Why this ?
And again another question. I drop my_table. I re-create my_Table with
this comm
and:
www=> create table sito (url varchar(255) PRIMARY KEY,
www-> titolo varchar(255), note varchar(64), indicazioni varchar(50),
genere int
,visto int, titolo_down varchar(255));\g
and psql return me:
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index sito_pkey for
table
sito
CREATE
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index sito_pkey for
table
sito
ERROR: amcreate: sito relation already exists
why the error?
tnx
"Non ��� importante che tu sia crotalo o pavone, l'importante ��� che
se tu muori me lo dici prima". (C���lv)
--
Michel <ZioBudda> Morelli michel@michel.enter.it
http://ziobudda.enter.it
Problemi con Linux ? mailto:linux@saturn.media.dsi.unimi.it
I don't know if this mailing list is the appropriate ML, but:
I think that in postgresql 6.3.2 there is a little bug.
I have a table. I exec:
alter table my_table add column mycolumn mytype\g
now if I make a select on this new column I get this errorERROR: RestrictionClauseSelectivity: bad value 2.350645
Otherwise, if I drop the my_table and recreate my_table with the new
column all
is work. Why this ?
Somehow the analyze statistics has goteen out of wack. Do a VACUUM
ANALYZE on the table, and the problem will go away. If can reproduce
the problem, please send the information to the hackers list. Thanks.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026