Re: 'now' doesnt seem to work in stored procedure

HK <harikrishnan@midascomm.com> writes:
> I am able to execute stored procedures. But sometimes i get this message.
> ERROR:  fmgr_info: cache lookup for language 1952725 failed

Sounds like you dropped the plpgsql language while there were still
functions that used it.  Not a good thing to do.

(7.3 will prevent you from making this class of mistake, btw)

> Inside a stored procedure i am using 'now' for a datetime value.
> Wat happens is when the stored procedure is loaded, the 'now' is
> initialised and afterwards whenever i use this procedure, the same value
> is being inserted.

Use now() or CURRENT_TIMESTAMP instead of 'now'.  The latter gets
reduced "on sight" to a timestamp constant.

            regards, tom lane