Re: [GENERAL] postgres crash when select a record

2008-05-15 Thread mailtolouis2020-postgres
Hello Pavel, Thanks for the info, this is very great help. Regard Louis - Original Message From: Pavel Stehule <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Postgres Sent: Thursday, May 15, 2008 4:43:36 AM Subject: Re: [GENERAL] postgres crash when select a record Hello 2008/5/14  <[

Re: [GENERAL] postgres crash when select a record

2008-05-14 Thread mailtolouis2020-postgres
Hello, Yes, I deleted that record, and now my backup is working fine! Thanks But why this problem came out? Is there anyway to trace it down and how it happen? Or is it a bug of postgres? Regards Louis - Original Message From: Pavel Stehule <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc:

Re: [GENERAL] postgres crash when select a record

2008-05-14 Thread mailtolouis2020-postgres
No, I didn't run the query when the DB is in recovering. I did that after database system is ready - Original Message From: Glyn Astill <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]; Postgres Sent: Wednesday, May 14, 2008 6:07:23 PM Subject: Re: [GENERAL] postgres crash when select a reco

[GENERAL] postgres crash when select a record

2008-05-14 Thread mailtolouis2020-postgres
Hello, I wish some could help me on this. I got a table which has 100500 records, when I try to query this particular record select * from cs_sr_mthly_rtn where mthly_rtn_id = 61609; Postgres crash, and show this errors: server closed the connection unexpectedly  This probably means the server te

[GENERAL] Duplicated primary key id happen

2008-05-09 Thread mailtolouis2020-postgres
Hello, I got a problem to restore a database, because there is a problem in my production database, which not suppose to happen like that, but it happen, not sure is a postgres bug or not. I got a table call CS_SR_MTHLY_RTN which has MTHLY_RTN_ID (INTEGER) as a primary key. So the MTHLY_RTN_ID v

[GENERAL] Duplicated primary key id happen

2008-05-09 Thread mailtolouis2020-postgres
Hello, I got a problem to restore a database, because there is a problem in my production database, which not suppose to happen like that, but it happen, not sure is a postgres bug or not. I got a table call CS_SR_MTHLY_RTN which has MTHLY_RTN_ID (INTEGER) as a primary key. So the MTHLY_RTN_ID v

[GENERAL] timestamp problem

2008-04-02 Thread mailtolouis2020-postgres
Hello, I got 2 database, one for product use and another for developer use. Both are same. In these database, I got a procedure which has a TIMSTAMP datatype as IN parameter. My problem is, when my Java application use the developer database and call this procedure, it is working fine, but w

Re: [GENERAL] Postgres file structure doubt

2007-11-20 Thread mailtolouis2020-postgres
Hello Scott, Thanks for clear my doubt. Yes, I'm planning to do PITR backup. Another question, from what I understand, when there are data transaction going on, postgres will store in the log file, which is in /usr/local/pgsql/data/pg_xlog, when these data will finally save it into /database/pg

[GENERAL] Postgres file structure doubt

2007-11-19 Thread mailtolouis2020-postgres
Hi everyone, Got a doubt in my setup, please correct me if I'm wrong. In my postgres setup, /usr/local/pgsql (where postgres install) /usr/local/pgsql/data (PGDATA) /database/pg/mydata (tablespace which use for all the table I create) /database/pg/myindex (index which use for all the table I cre

Re: [GENERAL] public schema doubt

2007-11-16 Thread mailtolouis2020-postgres
Hello Martin, Yes, SHOW search_path show this "$user",public . Oh yes, I get it now, the "$user" will take priority. Another question, this public schema, in the usual practice way, do you delete it or just leave it there and create your own schema? Regards Louis - Original Message

[GENERAL] public schema doubt

2007-11-16 Thread mailtolouis2020-postgres
Hello, I did a migration from 8.2.4 to 8.2.5, I used pg_dumpall to backup all the db and then restore it into 8.2.5. In my 8.2.4 db, I don't have public schema (it was dropped when I create the db, so only myschema is there), but when I restore to 8.2.5, I found that it created a public schema