In postgres you the plsql equivalent is 'plpgsql' not 'plsql'.
>> Original Message <<
On 3/05/02, 21:17:38, "jquest jquest" <[EMAIL PROTECTED]> wrote
regarding [ADMIN] Trigger problem:
> Hi,
> I am new to postgresql and to this moment I am using oracle.
> I use
Hello,A few minutes ago I had to cold reboot my machine (Red Hat 7.2) that was running PostgreSQL 7.2, as it (the machine) was hung (which is another PostgreSQL story that I'll explain separately).My attempt:[root@linux2 root]# /etc/rc.d/init.d/postgresql restartStopping postgresql service:
"otisg" <[EMAIL PROTECTED]> writes:
> Is there a way to get a more verbose error message from PostgreSQL that
> will tell me why I can't start the DB?
I'd venture that your /etc/rc script is preventing Postgres from telling
you anything useful. Try starting PG by hand ... or at the very least,
On Monday 06 May 2002 12:04 am, Tom Lane wrote:
> "otisg" <[EMAIL PROTECTED]> writes:
> > Is there a way to get a more verbose error message from PostgreSQL that
> > will tell me why I can't start the DB?
> I'd venture that your /etc/rc script is preventing Postgres from telling
> you anything us
Thank you, this was it.Otis___Sign up for FREE iVillage newsletters.From health and pregnancy to shopping and relationships, iVillagehas the scoop on what matters most to you.
<-Original Message->> > From: tulasi> Sent: 5/6/2002
On Monday 06 May 2002 12:03 am, Lamar Owen wrote:
> For debugging purposes, either editing /etc/rc.d/init.d/postgresql to
> change the output redirect, or enabling syslog as documented in
> /usr/share/doc/postgresql-7.2 (or 7.2.1, as applicable).
Urgh. Append 'README.rpm-dist' to that path.
--
Hello,I am having problems keeping PostgreSQL alive in certain situations and I wonder if I can tune some parameters to allow it to handle higher load.What gets logged in syslog log file are things like this:May 5 21:52:34 localhost postgres[25012]: [64] NOTICE: TRANSACTION ISOLATION LEVEL is REA
