home :: software :: postgresql

Tue, 06 Mar 2007

postgresql forward / backward incompatibilities

Today I had "ERROR: column i.indisvalid does not exist" appear in both a client system and on the database backend. My initial searching lead me to a possible problem in pgpool but since I don't use that, that couldn't be it. I quickly jumped onto #postgresql on Freenode and the guys there (specifically Gavin Sherry) suggested it was either because I hadn't vacuum'd the database -- in my case I have autovacuum on -- OR there was a version mismatch between client and server. It turns out it was the later: client was 8.2 and server was 8.1 From time to error to solution was 15 mins -- that's what support is all about. Awesome. I'm just blogging this here so that in case anyway else gets the same error there is a chance a search engine might return a useful result.

[ / software] Trackbacks (0) Comments (0) permanent link permanent link

Trackbacks

Trackbacks are closed for this story.

Comments

Submit a comment

Comments are closed for this story.

About

ॐ (aum) - what was, what is and what will be, wildfire's musing

Anand Kumria
wildfire@progsoc.org

Calendar

Topics

beauty - 1
blogging - 3
books - 1
debian - 6
freedom - 2
general - 2
hardware - 3
dell - 2
disks - 1
helsinki - 1
security - 1
software - 16
blosxom - 2
moblog - 1
vcs - 2
zeroconf - 1
sydney - 5
travel - 1
work - 2
awayphone - 1
general - 1

Subscribe

Subscribe to a syndicated feed of my weblog, brought to you by the wonders of Atom.

Music

Blosxom

Rendered in only 0.0399 seconds.

ॐ (aum) - what was, what is and what will be