From: | Ricardo Bayley <ricardo(dot)bayley(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: NEW + tableOID |
Date: | 2010-08-13 22:05:39 |
Message-ID: | AANLkTinTMX3xie2CVTHfhJ+itnZ5H5i1jsnQQ6e8tVz+@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Tom that was exactly what I was looking for.
Do you think that having just 1 table to perform the Full Text Search is a
better approach than having 1 master table with child tables, and always
querying the Master one ? Which do you believe is faster ?
regards
On Fri, Aug 13, 2010 at 6:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ricardo Bayley <ricardo(dot)bayley(at)gmail(dot)com> writes:
> > I do this with triggers. This issue I have is that the tableoid data
> cannot
> > be used with the NEW keyword. I always get value 0 instead of the actual
> > tableoid.
>
> That might work in an AFTER trigger, but it definitely won't work in a
> BEFORE trigger, because the NEW row isn't actually part of the table at
> that point. You'd probably be better off to rely on the trigger
> function TG_RELID parameter instead, anyway.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sivaroj Limvipuwat | 2010-08-14 03:34:10 | Can't start server |
Previous Message | Tom Lane | 2010-08-13 21:45:05 | Re: NEW + tableOID |