Martijn van Oosterhout <kleptog@svana.org> writes: > As per discussion on -hackers, type input functions can be called prior > to there being a current snapshot, causing any queries you execute to > fail with the "no snapshot has been set" error. So I propose to simply > have SPI_connect fail right off the bat and document that to avoid > future surprises.
This strikes me as a pretty unreasonable restriction. It would be OK if there were no valid uses of SPI that didn't require a snapshot, but that's not so. As an example, consider trying to issue a LOCK TABLE command via SPI (okay, there are other ways to do that, but it's still a valid example). regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly