Re: trigger compile problem

From: T(dot)R(dot)Missner(at)Level3(dot)com
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: JanWieck(at)Yahoo(dot)com, doug(at)wireboard(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: trigger compile problem
Date: 2001-09-26 05:30:03
Message-ID: EBFCF3982143D511A77F0008C716807E0106DB32@N0400IDC1.oss.level3.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

one more note. A lot of things I have read comparing pgsql
to mysql have stated that one of the weaknesses of pgsql is insert speed.
Well I am developing a near real time signaling analyzer and am currently
inserting over 100 rows per sec which include blobs. I thinki I can push it
even higher
and will kepp you posted on the results if you are interested.

t.r. missner
level(3) communications

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, September 25, 2001 11:23 PM
To: Missner, T. R.
Cc: Jan Wieck; doug(at)wireboard(dot)com; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] trigger compile problem

T(dot)R(dot)Missner(at)Level3(dot)com writes:
> It was the ; after END
> I feel like a tard.
> spent over 5 hours on this .

I've always wondered why plpgsql is so nitpickingly insistent on finding
a semicolon after the last END. Would anyone object if I made the
last semi optional?

regards, tom lane

Browse pgsql-general by date

  From Date Subject
Next Message tony 2001-09-26 07:58:01 Re: Multibyte FAQ item
Previous Message T.R.Missner 2001-09-26 05:25:45 Re: trigger compile problem