While you guys are still awake, I may as well ask this:
I gather that the following code goes though the heap and removes all check
contraints associated with a particular table, but how do I extend the code
to match both a table relid and the constraint name? Basically I'm just
asking how I express 'SQL SELECT' queries using the heap access functions?
rcrel = heap_openr(RelCheckRelationName, RowExclusiveLock);ScanKeyEntryInitialize(&key, 0, Anum_pg_relcheck_rcrelid,
F_OIDEQ, RelationGetRelid(rel));
rcscan = heap_beginscan(rcrel, 0, SnapshotNow, 1, &key);
while (HeapTupleIsValid(tup = heap_getnext(rcscan, 0))) simple_heap_delete(rcrel, &tup->t_self);
heap_endscan(rcscan);heap_close(rcrel, RowExclusiveLock);
Cheers,
Chris
> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Friday, 11 May 2001 10:43 AM
> To: Hiroshi Inoue
> Cc: Bruce Momjian; Philip Warner; The Hermit Hacker;
> PostgreSQL-development
> Subject: Re: [HACKERS] 7.1.2 release
>
>
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > I agree with you because the bug is very critical.
>
> Yes, I'd like to get that plpgsql bug fix out as soon as possible.
>
> But the pg_dump things that Philip is fixing are important too,
> so I think we should wait a couple more days for those.
> (Philip, we are just talking about a few days, right?)
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
