X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 6E3DAD9CB2
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Tue, 11 Oct 2005 00:10:53 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 52700-02
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Tue, 11 Oct 2005 03:10:51 +0000 (GMT)
Received: from mail.nsasia.co.th (mail.nsasia.co.th [203.146.6.34])
	by svr1.postgresql.org (Postfix) with ESMTP id E9A34D9FF2
	for <pgsql-sql@postgresql.org>; Tue, 11 Oct 2005 00:10:49 -0300 (ADT)
Received: from [192.168.200.39] (helo=mail.nsasia.co.th)
	by astaro.nsasia.co.th with esmtp (Exim 4.43) id 1EPAXQ-0000hn-54
	for pgsql-sql@postgresql.org; Tue, 11 Oct 2005 10:10:48 +0700
Received: from Thailand-MTA by mail.nsasia.co.th
	with Novell_GroupWise; Tue, 11 Oct 2005 10:10:33 +0700
Message-Id: <434B8F91.C5F7.004C.0@nsasia.co.th>
X-Mailer: Novell GroupWise Internet Agent 7.0 
Date: Tue, 11 Oct 2005 10:10:26 +0700
From: "Premsun Choltanwanich" <Premsun@nsasia.co.th>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Richard Huxton" <dev@archonet.com>, <pgsql-sql@postgresql.org>
Subject: Re: How to delete Large Object from Database?
References: <43465BAA.C5F7.004C.0@nsasia.co.th>
 <434623FD.7000408@archonet.com>
	<434A8F85.C5F7.004C.0@nsasia.co.th> <434A3D2F.90907@archonet.com>
	<434B81B8.C5F7.004C.0@nsasia.co.th><434B81B8.C5F7.004C.0@nsasia.co.th>
	<8632.1128999653@sss.pgh.pa.us>
In-Reply-To: <8632.1128999653@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part7F5D7A32.1__="
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.193 required=5 tests=[AWL=-0.071, HTML_30_40=0.056,
	HTML_MESSAGE=0.001, UPPERCASE_25_50=0.207]
X-Spam-Level: 
X-Archive-Number: 200510/81
X-Sequence-Number: 22934

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=__Part7F5D7A32.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Sorry that I forgot to sent you trigger on my database.
=20
CREATE OR REPLACE FUNCTION lo_manage()
  RETURNS "trigger" AS
'$libdir/lo', 'lo_manage'
  LANGUAGE 'c' VOLATILE;
ALTER FUNCTION lo_manage() OWNER TO postgres;
=20


>>> Tom Lane <tgl@sss.pgh.pa.us> 11-Oct-05 10:00:53 am >>>
"Premsun Choltanwanich" <Premsun@nsasia.co.th> writes:
> The code that show below is refered to table and function that I use for =
=3D
> kept BLOB (LO).
> =20
> CREATE TABLE t_data_pic
> (
>   "sysid" bigserial NOT NULL,
>   data_sysid int8 NOT NULL,
>   data_pic lo,
>   CONSTRAINT t_data_pic_pkey PRIMARY KEY ("sysid")
> )=20
> WITH OIDS;
> ALTER TABLE t_data_pic OWNER TO admin;

Why am I not seeing any trigger attached to this table?  That lo_manage
trigger is the useful part of contrib/lo --- the separate data type is
mere window dressing.

regards, tom lane


--=__Part7F5D7A32.1__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-874=
">
<META content=3D"MSHTML 6.00.2900.2604" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Sorry that I forgot to sent you trigger on my database.</DIV>
<DIV>&nbsp;</DIV>
<DIV>CREATE OR REPLACE FUNCTION lo_manage()<BR>&nbsp; RETURNS "trigger" =
AS<BR>'$libdir/lo', 'lo_manage'<BR>&nbsp; LANGUAGE 'c' VOLATILE;<BR>ALTER =
FUNCTION lo_manage() OWNER TO postgres;</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR><BR>&gt;&gt;&gt; Tom Lane &lt;tgl@sss.pgh.pa.us&gt; 11-Oct-05 =
10:00:53 am &gt;&gt;&gt;<BR>"Premsun Choltanwanich" &lt;Premsun@nsasia.co.t=
h&gt; writes:<BR>&gt; The code that show below is refered to table and =
function that I use for =3D<BR>&gt; kept BLOB (LO).<BR>&gt;&nbsp; <BR>&gt; =
CREATE TABLE t_data_pic<BR>&gt; (<BR>&gt;&nbsp;&nbsp; "sysid" bigserial =
NOT NULL,<BR>&gt;&nbsp;&nbsp; data_sysid int8 NOT NULL,<BR>&gt;&nbsp;&nbsp;=
 data_pic lo,<BR>&gt;&nbsp;&nbsp; CONSTRAINT t_data_pic_pkey PRIMARY KEY =
("sysid")<BR>&gt; ) <BR>&gt; WITH OIDS;<BR>&gt; ALTER TABLE t_data_pic =
OWNER TO admin;<BR><BR>Why am I not seeing any trigger attached to this =
table?&nbsp; That lo_manage<BR>trigger is the useful part of contrib/lo =
--- the separate data type is<BR>mere window dressing.<BR><BR>regards, tom =
lane<BR></DIV></BODY></HTML>

--=__Part7F5D7A32.1__=--