No, I have lots of calls to current_timestamp inside volatile functions which lock tables without complaints. I am beginning to think I hit some sort of bug. This is PostgreSQL 9.0.1.
On Tue, Apr 17, 2012 at 5:55 PM, Michael Nolan <htf...@gmail.com> wrote: > > > On Tue, Apr 17, 2012 at 5:20 PM, Eliot Gable <ega...@gmail.com> wrote: > >> >> >> >> I cannot find a single non-volatile function in the call path; so I am >> baffled on where this error message is coming from. I would be thankful for >> any ideas anyone might have on where this error message might be coming >> from or how to locate where it is coming from. >> >> >> According to the documentation, the current_timestamp family of functions > is stable, could that be the cause? Better yet, should it? > -- > Mike Nolan > -- Eliot Gable "We do not inherit the Earth from our ancestors: we borrow it from our children." ~David Brower "I decided the words were too conservative for me. We're not borrowing from our children, we're stealing from them--and it's not even considered to be a crime." ~David Brower "Esse oportet ut vivas, non vivere ut edas." (Thou shouldst eat to live; not live to eat.) ~Marcus Tullius Cicero
