Re: ERROR: fmgr_info: function 24809: cache lookup failed
От
Jessica Blank
Тема
Re: ERROR: fmgr_info: function 24809: cache lookup failed
Дата
Msg-id
Pine.LNX.4.44.0212181305380.392-100000@ensim.rackshack.net
Ответ на
Re: ERROR: fmgr_info: function 24809: cache lookup (Oliver Elphick)
Список
Дерево обсуждения
ERROR: fmgr_info: function 24809: cache lookup failed Jessica Blank <jb@twu.net>
Re: ERROR: fmgr_info: function 24809: cache lookup Oliver Elphick <olly@lfix.co.uk>
Re: ERROR: fmgr_info: function 24809: cache lookup failed Jessica Blank <jb@twu.net>
Re: ERROR: fmgr_info: function 24809: cache lookup failed Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
Re: ERROR: fmgr_info: function 24809: cache lookup failed Tariq Muhammad <tmuhamma@libertyrms.com>
Many thanks to Oliver and the several others who provided similar information. :) I will implement that, yes. Still, it would be nice to know how you CAN make triggers/functions/whatnot do what I wanted.. if only for education's sake. :) On 17 Dec 2002, Oliver Elphick wrote: > On Tue, 2002-12-17 at 13:03, Jessica Blank wrote: > > Hi all. I feel awfully stupid. > > > > Migrating my skillset from Oracle to Postgres, I am trying (in vain) to > > create a trigger and a sequence to "auto increment" the primary key in a > > table, so I won't have to worry about setting it; each time you INSERT > > into the table, the primary key will be automagically assigned. > > As Jessica said, use the SERIAL type, which will automatically increment > the sequence and use its value unless an explicit value is given for the > column. > > > And when I try to INSERT into SENTENCES, without my SENTENCEID, hoping > > that the function/trigger/sequence will kick in and assign it for me... > > > > architxts=# INSERT INTO SENTENCES (CHAPTERID, SOFFSET) VALUES (123, 147); > > ERROR: fmgr_info: function 24809: cache lookup failed > > This probably means that you have dropped and recreated the function > after you created the trigger. The trigger is still looking for the old > function, but it has been deleted. To avoid such problems, use CREATE > OR REPLACE FUNCTION ... If you haven't got that syntax available, you > need to update PostgreSQL. > > -- J e s s i c a L e a h B l a n k
В списке pgsql-general по дате отправления