[GENERAL] Re: Postgres concurrency : urgent

1999-11-11 Thread Vadim Mikheev
V Krishnaraj wrote: > > After a few times, there lots of messages are spewed out in the postgres > server log. A typical message looks like this. > NOTICE: Message from PostgreSQL backend: > The Postmaster has informed me that some other backend died abnormally a > nd possibly corrupted shared me

[GENERAL] Re: Postgres concurrency : urgent

1999-11-11 Thread V Krishnaraj
Hi, Thanks for looking into the problem immediately. I'll answer all questions that have been raised 1. What error message does it put out I'm getting 2 messages. First message is 'ERROR: Can't serialize access due to concurrent update'. This is perfect. I am trying to access already locked ro

Re: [GENERAL] Postgres concurrency : urgent

1999-11-11 Thread Vadim Mikheev
V Krishnaraj wrote: > > This application works fine when we are in single user. When we > go into multi-user, the app has concurrency problems. > > The application has a sql query and updates onto the base table in > the sql query. We are using Select FOR UPDATE to open the > cursor and multiple

Re: [GENERAL] Postgres concurrency : urgent

1999-11-11 Thread Vadim Mikheev
Marcin Inkielman wrote: > > I 'm using : > > LOCK <> IN ACCESS EXCLUSIVE MODE; ^^ This blocks concurrent read access - is it what you really want? > to control concurrent transactions - it works for me > (postgres 6.5.2) Vadim

Re: [GENERAL] Large database problems

1999-11-11 Thread Myles Chippendale
All, Problem solved. We upgraded glibc as well, but didn't recompile readline. Well, at least the problem's fixed. Myles At 09:18 PM 11/10/99 +, Myles Chippendale wrote: >All, > >We are having a few problems with a large database in postgres 6.5.2 >under Linux 2.2.13 (upgraded from RedHat

[GENERAL] How to enable PL/pgsql for functions/triggers

1999-11-11 Thread Ed Loehr
I wanted to use PL/pgsql to write functions for use with triggers, and thought others might benefit from a concise description of how to enable this without having to scour the postgresql documentation. This was with a default install of pgsql v6.5.2 on RH6.0. CREATE FUNCTION plpgsql_call_h

Re: [GENERAL] Postgres concurrency : urgent

1999-11-11 Thread Marcin Inkielman
On Fri, 12 Nov 1999, V Krishnaraj wrote: > Hi, > > I'm having a postgres database accessed from perl using DBI and > DBD. > > This application works fine when we are in single user. When we > go into multi-user, the app has concurrency problems. > > The application has a sql query and update

[GENERAL] Postgres concurrency : urgent

1999-11-11 Thread V Krishnaraj
Hi, I'm having a postgres database accessed from perl using DBI and DBD. This application works fine when we are in single user. When we go into multi-user, the app has concurrency problems. The application has a sql query and updates onto the base table in the sql query. We are using Select

[GENERAL] postgres can't connect to specific database.

1999-11-11 Thread Natalya S. Makushina
Hi all! I have a very strange problem. Connect to specific database can't established. This is the part of my log file: Nov 11 18:09:00 application postgres[1401]: read_pg_options: all=0,verbose=1,plan=0,rewritten=0,query=1,syslog=2,locks=0 ,hostlookup Nov 11 18:09:00 application postgres[1401

[GENERAL] Problem with C functions ?

1999-11-11 Thread Manuel Weindorf
Hi there, I compiled a C-funtion to compute the azimuth of a LSEG but the function never returns the correct value, but elog( ... ) report the correct value. So there seems to be a problem returning doubles or floats ?? compile the folling function with gcc -fPIC -O2 -shared -o lseg_azimuth.o -