On Wed, 4 Apr 2001, Tom Lane wrote:
> Cedar Cox <[EMAIL PROTECTED]> writes:
> > And I get this notice:
> 
> >   NOTICE:  PortalHeapMemoryFree: 0x0x824a6e8 not in alloc set!
> >   NOTICE:  Buffer Leak: [059] (freeNext=54, freePrev=58, relname=tblstsc1,
> > blockNum=0, flags=0x14, refcount=-4 -1)
> 
> (a) What Postgres version is this?
> 
> (b) Could we see the schemas for the tables?  (pg_dump -s output is the
> best way)

Ver 7.0.2 (sorry, I meant to include this... I think)

Attached is (b).  I have all kinds of horrid custom RI triggers.  I can
send the whole DB schema if necessary.

-Cedar
CREATE TABLE "tblstsc1" (
        "surid" character varying(50) NOT NULL,
        "sc1strictnessid" int4 NOT NULL,
        "sc1caption" text,
        "defaultoptionid" int4 NOT NULL,
        CONSTRAINT "tblstsc1_sc1caption" CHECK ((sc1caption <> ''::text)),
        PRIMARY KEY ("surid")
);
CREATE TRIGGER "tblstsc1_before" BEFORE INSERT OR DELETE OR UPDATE ON "tblstsc1"  FOR 
EACH ROW EXECUTE PROCEDURE "tblstsc1_before" ();
CREATE CONSTRAINT TRIGGER "<unnamed>" AFTER INSERT OR UPDATE ON "tblstsc1"  NOT 
DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE PROCEDURE "RI_FKey_check_ins" 
('<unnamed>', 'tblstsc1', 'tblidstrictness', 'UNSPECIFIED', 'sc1strictnessid', 
'strictnessid');

CREATE TABLE "tblstsc1options" (
        "sc1optionid" int4 NOT NULL,
        "sc1optionname" character varying(50) NOT NULL,
        "sc1optionvalue" float4,
        "surid" character varying(50) NOT NULL,
        CONSTRAINT "tblstsc1options_sc1optionvalue" CHECK ((sc1optionvalue > 0)),
        CONSTRAINT "tblstsc1options_sc1optionname" CHECK ((sc1optionname <> 
''::"varchar")),
        PRIMARY KEY ("sc1optionid")
);
CREATE  INDEX "ix_stsc1options_surid" on "tblstsc1options" using btree ( "surid" 
"varchar_ops" );
CREATE TRIGGER "tblstsc1options_before" BEFORE INSERT OR DELETE OR UPDATE ON 
"tblstsc1options"  FOR EACH ROW EXECUTE PROCEDURE "tblstsc1options_before" ();

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to