[ADMIN] Migration Problems 7.2.3 -> 7.3.4

Good afternoon, I searched the archives and since I'm a relatively noivce user I'll have to run the risk of repeating already asked questions. I'm having a problem on two counts with migrating our database. Firstly the existing database is encoded as SQLASCII in which the majority of characters

[ADMIN] Matching indexes on int8 columns

I'm running 7.3, and I recently found out something rather disconcerting: if I have an index on an int8 column, and I run a query such as SELECT * FROM [tablename] WHERE [colname] = 12345 the index is NOT used, and sequential scan of the 200K rows is done, taking ~ 17500 msec.; if I ch

Re: [ADMIN] Access with a management tool

I could add the question: where must the postgresql.conf file be located. I only have it under a var/lib-folder Regards Per "Per Münster" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] > I have got a tool for managing the postgres from postgres. When trying to > register server

Re: [ADMIN] Access with a management tool

I found out that I have got 3 conf-files all located in the /var/lib/pgsql library, which to my eyes seem to be the right. The postgresql.conf has the port 5432 mentionend and the service is running all right. But I can not connect. /Per "Per Münster" <[EMAIL PROTECTED]> skrev i en meddelelse news

[ADMIN] transaction-wraparound data loss

Brian E. Pangburn asked some time ago about getting the warning WARNING: Some databases have not been vacuumed in over 2 billion transactions. You may have already suffered transaction-wraparound data loss. while doing a routine vacuum. Tom Lane answered but did not have an answer right

[ADMIN] Access with a management tool

I have got a tool for managing the postgres from postgres. When trying to register server and/or database I get the message, that I should check if the server is listening on 5432. Well, I do not really know. I know only that I've got access from a linux shell, but I am trying to operate from a wi

Re: [ADMIN] transaction-wraparound data loss

See section 8.2.3 of the admin guide (v7.3) "Preventing transaction ID wraparound failures" - Original Message - From: "Ari Jolma" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 24, 2003 1:44 AM Subject: [ADMIN] transaction-wraparound data loss > Brian E. Pangburn as

Re: [ADMIN] Access with a management tool

edit your pg_hba.conf regards, Oli -Ursprüngliche Nachricht- Von: Per Münster [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 24. Oktober 2003 12:32 An: [EMAIL PROTECTED] Betreff: [ADMIN] Access with a management tool I have got a tool for managing the postgres from postgres. When trying

Re: [ADMIN] Access with a management tool

if it's a pg_hba issue, he should get a FATAL "authentication failed"-ish message. I'd check for tcpip_socket=true in postgresql.conf first. Robert Treat On Fri, 2003-10-24 at 11:00, Oliver Scheit wrote: > edit your pg_hba.conf > > regards, > Oli > > -Ursprüngliche Nachricht- > Von: Pe

[ADMIN] device full ---> postgres will not start

Hello:   It looks like I got caught sleeping.   I am running Postgresql 7.2 under Red Hat 7.3. Postgresql failed today.  When I tried to restart it, I got a message stating that the device is full. I used df to confirm that /var where postgres reside is full.  /var is on a 4 Gig device. Po