Re: [GENERAL] Core reported from vaccum function.

: Mavinakuli, Prasanna (STSD) Cc: Alvaro Herrera; pgsql-general@postgresql.org; Rao, Srikanth R (STSD); Racharla, Chakravarthy (STSD); Manchenahalli, Raghunandan (STSD); Hebbar, Raghavendra (STSD) Subject: Re: [GENERAL] Core reported from vaccum function. "Mavinakuli, Prasanna (STSD)" <[EM

Re: [GENERAL] Core reported from vaccum function.

upgrade. Thanks, Prasanna. -Original Message- From: Alvaro Herrera [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 7:18 PM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org; Tom Lane; Rao, Srikanth R (STSD); Racharla, Chakravarthy (STSD); Manchenahalli, Raghunandan (STSD

Re: [GENERAL] Core reported from vaccum function.

Fine.Thanks for all your suggestions and time. Thanks a lot, Prasanna. -Original Message- From: Alvaro Herrera [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 01, 2007 8:48 AM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org; Tom Lane; Rao, Srikanth R (STSD); Racharla

Re: [GENERAL] Core reported from vaccum function.

a lot, Thanks , Prasanna. -Original Message- From: Alvaro Herrera [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 10:00 PM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org; Tom Lane; Rao, Srikanth R (STSD); Racharla, Chakravarthy (STSD); Manchenahalli, Raghunandan

Re: [GENERAL] Core reported from vaccum function.

been done etc? Thanks a lot for all your help/time. Thanks, Prasanna. -Original Message- From: Alvaro Herrera [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 19, 2007 8:44 AM To: Mavinakuli, Prasanna (STSD) Cc: Tom Lane; pgsql-general@postgresql.org; Rao, Srikanth R (STSD) Subject: Re: [GEN

[GENERAL] Restoring the DB from others user DB Backup.

Hello, We have 2 altogether databases owned by two different users.The requirement is ,by using a back up dump of a database owned by some other user,We will need to restore the other DB which is owned completely by other user. The problem what we are facing is,if we try to use pg_restore command

[GENERAL] Looking for help regarding getting the latest inserted sequence value.

Hello All, We are looking for your help.The scenarion which we need to address is,There are 2 threads and both of them are in separate transction and insert the value to a same table and also sequence number field gets incremented automotically for each of them.The problem we are facing is,We will

[GENERAL] Core reported from vaccum function.

Hello All, We are getting the following core more oftenly.But We don't have a test case where it is guaranteed to dump this core.We are using 7.4.2 version postgres and if any one of you aware about some bug fixes happened around this problem.Please let us know. Thanks, Prasanna. Core was genera

[GENERAL] Too many open files from postgres.

Hello All, We are using postgres with HP-UX. Usually We will have many records,and will do vacuum once in 2 days. We have observed that postgres opens many files in data directory And won't close till next vacuum (I experience it) When it hits max limit, we won't able to open any other files. S

Re: [GENERAL] Too many open files from postgres.

Also (obvsly) we aren't able to get a new connection after hitting max fd limit.. Thx, Prasanna. -Original Message- From: Mavinakuli, Prasanna (STSD) Sent: Wednesday, August 09, 2006 10:10 AM To: pgsql-general@postgresql.org Cc: Mavinakuli, Prasanna (STSD) Subject: Too many open

[GENERAL] Syslog v/s filename in pg_ctl command

Hello All, When we pass file name in pg_ctl (with option -l) what has to be syslog value.. Should it be enabled..?if so what cud be the value for syslog..? Though I have sent approprite file name with -l option ,and if I use default value for syslog (0) then I am getting the messages in console.

Re: [GENERAL] HUGE Stack space is gettiing consumed

Hello Martijin, I have one more doudt ..while building libpq.so we are not specifying --enable-thread-safety Will it make any difference..? Thx, Prasanna. -Original Message- From: Mavinakuli, Prasanna (STSD) Sent: Friday, April 21, 2006 5:46 PM To: 'Martijn van Oosterhout

Re: [GENERAL] HUGE Stack space is gettiing consumed

Tuesday, April 18, 2006 2:46 PM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] HUGE Stack space is gettiing consumed On Tue, Apr 18, 2006 at 12:31:57PM +0530, Mavinakuli, Prasanna (STSD) wrote: > Hello Martijin, > Thx for u'r Suggetions.. > &

Re: [GENERAL] HUGE Stack space is gettiing consumed

e #include #include void* queryDB(void* p) { cout<<"I Am in Routine Function *** "<mailto:[EMAIL PROTECTED] Sent: Saturday, April 15, 2006 7:22 PM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] HUGE Stack space is gettiin

[GENERAL] HUGE Stack space is gettiing consumed

Hello All, We are getting very strange problem .. Scenario.. We Have one data field in some table..type of this field Is *TEXT*. We are storing around 1,000 (One Thousand) lines of text In that field. If it's run though separate thread,

[GENERAL] Strange error while executing query from front end:

Hi, I am getting following strange errors while executing queries. 1) ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only to 0/1813C60 CONTEXT: writing block 2 of relation 17142/16653 WARNING: could not write block 2 of 17142/16653 DETAIL: Multiple failures --- write error

Re: [GENERAL] Strange error while executing query from front end:

Exact message of my second problem is: WARNING: relation "rawlog" page 0 is uninitialized --- fixing -Original Message----- From: Mavinakuli, Prasanna (STSD) Sent: Monday, January 16, 2006 9:28 AM To: pgsql-general@postgresql.org Subject: Strange error while executing query

Re: [GENERAL] Strange error while executing query from front end:

30 is uninitialized --- fixing WARNING: relation "rawlog" page 29 is uninitialized --- fixing WARNING: relation "rawlog" page 31 is uninitialized --- fixing WARNING: relation "rawlog" page 30 is uninitialized --- fixing WARNING: relation "rawlog" page 3

[GENERAL] Not able to insert the large data to HP-UX IA machines

Hi, We are supposed to insert the large data which is around 200 k/row. (Through libpq) We are able to do it in HP-UX PA machines.not in HP-UX IA machines. We can insert the data upto 46k in IA machines.(we have bytea field .and most(all) of data go to this field) When we try to insert the large

Re: [GENERAL] LOG: unexpected EOF within message length word

for(int kk=0;kkmailto:[EMAIL PROTECTED] Sent: Saturday, September 03, 2005 11:08 AM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] LOG: unexpected EOF within message length word On Sat, Sep 03, 2005 at 09:29:20AM +0530, Mavinakuli, Prasanna (STSD)

Re: [GENERAL] LOG: unexpected EOF within message length word

. = 1 write(1, "\n", 1) .. = 1 write(1, "\n", 1) ........ .. = 1 constructing result set objectwri

Re: [GENERAL] LOG: unexpected EOF within message length word

mTypes,paramValues,paramLengt hs,paramFormats,resultFormat); res1=PQexec(conn,"select * from rawlog"); for(int kk=0;kkmailto:[EMAIL PROTECTED] Sent: Friday, September 02, 2005 7:45 PM To: Mavinakuli, Prasanna (STSD) Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL]

[GENERAL] LOG: unexpected EOF within message length word

Hi, When I try to insert the data of size 40764 bytes(data type bytea) the call PQexecparams won't return and when I kill that one it gives The log:"LOG: unexpected EOF within message length word" Or "Log:Incomplete message transfer from client". If I try to insert data of size 40760 bytes (data

[GENERAL] PQexecParams-Problem

Hi, Problem Description: We need to insert binary data to tables and retrieve the Same-(data type is bytea). We are using PQExecParams for inserting and retrieving Data. Table contains other than binary data also. When we tried to fetch the integer data (type-int2) We are not able to get anyt