Add a FROM opposite-relname after the ON relname to
the CREATE CONSTRAINT TRIGGER statements. That's it.
I'll make the change ASAP.
I'm about to do this - does anyone object to me adding the 7.0 backward
compatibility changes at the same time?
Bruce Momjian wrote:
Postgresql Programmer's Guide
by Thomas Lockhart, Thomas Lochart (Editor)
http://www.amazon.com/exec/obidos/ASIN/0595149170/ref=pd_sim_elt_l1/107-6921356-0996510
Oh! Have you changed the PostgreSQL logo to an unplugged old macintosh
mouse ?
-
Hannu
Got a query that looks like:
SELECT card_info.main_cat, category_details.sub_cat_flag,count(*)
FROM send0,card_info,category_details
WHERE send0.card_id=card_info.card_id
AND category_details.mcategory='e-cards'
hi, there!
On Mon, 23 Apr 2001, Jan Wieck wrote:
I just got trapped by one of my own features in the
referential integrity area.
The problem is, that the trigger run on the FK row at UPDATE
allways checks and locks the referenced PK, even if the FK
Tom:
Notice that WriteBuffer would just put the fresh copy of the page
out in the shared space.
Other backends would get the latest copy of the page when
THEY execute BufferAlloc() afterwards. [Remember, backends would
not have a local buffer cache, only (temporary) copies of one buffer
You will find that that script is not distributed by us.
[ Charset ISO-8859-1 unsupported, converting... ]
Hi,
I believe i found two minor bugs in the linux start/stop scripts for the
downloadable rpm version of postgres 7.1. I don't think these have been
reported already (i did some
Tom Lane writes:
The Hermit Hacker [EMAIL PROTECTED] writes:
sendmail does it now, and, apparently relatively portable across OSs ...
sendmail expects to be root. It's unlikely (and very undesirable) that
postgres will be installed with adequate privileges to read /dev/kmem,
which is
SELECT card_info.main_cat, category_details.sub_cat_flag,count(*)
FROM send0,card_info,category_details
WHERE send0.card_id=card_info.card_id
AND category_details.mcategory='e-cards'
AND card_info.main_cat=category_details.category
AND send_date = '2001/04/08'
AND send_date
Apparently so under Solaris ...
hestia:/ uname -a
SunOS hestia 5.7 Generic_106542-12 i86pc i386 i86pc
C Library Functionsgetloadavg(3C)
NAME
getloadavg - get system load averages
SYNOPSIS
#include sys/loadavg.h
int getloadavg(double loadavg[],
Doug McNaught wrote:
A very valid objection. I'm also dubious as to the utility of the
whole concept. What happens when Sendmail refuses a message based on
load? It is requeued on the sending end to be tried later. What
happens when PG refuses a new client connection based on load? The
Doug McNaught writes:
A very valid objection. I'm also dubious as to the utility of the
whole concept. What happens when Sendmail refuses a message based on
load? It is requeued on the sending end to be tried later. What
happens when PG refuses a new client connection based on load? The
Max Khon wrote:
hi, there!
On Mon, 23 Apr 2001, Jan Wieck wrote:
I just got trapped by one of my own features in the
referential integrity area.
The problem is, that the trigger run on the FK row at UPDATE
allways checks and locks the referenced PK,
who is it distributed by then? it was on the postgres ftp mirror sites, so
it probably can't be redhat. I have found workarounds, so its not a big
deal, but... Also, i wonder what else is different from this package from
the real source distribution. I am sorry if this has been discussed or
I would like to know myself. I just did a recursive grep of the entire
PostgreSQL tree and don't see it. My guess is that it is part of the
RPM. Not sure who to report that to. I know Lamar Owen works on it,
but I don't know if he is the contact.
[ Charset ISO-8859-1 unsupported,
Bruce Momjian wrote:
I would like to know myself. I just did a recursive grep of the entire
PostgreSQL tree and don't see it. My guess is that it is part of the
RPM. Not sure who to report that to. I know Lamar Owen works on it,
but I don't know if he is the contact.
Yes, that would be
Does anybody know:
1) Is the tar/custom format of pg_dump is portable accross different
platforms?
2) if I want to dump out all of database cluster contents including
large objects, is following procedure correct?
(dump procedure)
pg_dumpall -g
pg_dump -F c for each
On Wed, 25 Apr 2001, Lincoln Yeoh wrote:
At 10:59 PM 23-04-2001 -0700, Nathan Myers wrote:
On Tue, Apr 24, 2001 at 12:39:29PM +0800, Lincoln Yeoh wrote:
Why not be more deterministic about refusing connections and stick
to reducing max clients? If not it seems like a case where you're
At 12:04 25/04/01 +1000, Philip Warner wrote:
it won't currently work if
multiple dumps are being sent to stdout.
This latter could be fixed (at least for 'c' format) by modifying pg_dump
to use open/read/write/lseek instead of fopen/fread/fwrite/fseek etc.
At 11:28 PM 24-04-2001 -0300, The Hermit Hacker wrote:
I have a Dual-866, 1gig of RAM and strip'd file systems ... this past
week, I've hit many times where CPU usage is 100%, RAM is 500Meg free and
disks are pretty much sitting idle ...
It turns out, in this case, that vacuum was in order (i
19 matches
Mail list logo
