"Eric B. Ridge" <[EMAIL PROTECTED]> writes:
> The tuplestore stuff sounds like the right solution, but in the
> interests of providing a quick patch to my production environment does
> it makes sense to make a copy of the SPI_tuptable during the first-call
> of the SRF (allocated in the SRF's me
On Apr 1, 2005, at 3:55 PM, Tom Lane wrote:
"Eric B.Ridge" <[EMAIL PROTECTED]> writes:
Like I said, everything
usually works without problems, but from time to time it crashes.
If you rebuild with --enable-cassert, does the crash get more
reproducible?
Indeed. Every time. This is now the default
"Eric B.Ridge" <[EMAIL PROTECTED]> writes:
> Like I said, everything
> usually works without problems, but from time to time it crashes.
If you rebuild with --enable-cassert, does the crash get more
reproducible? (Personally I would never consider developing any
backend C code without that tur
With pg v7.4.7 I've written an SRF that uses SPI to return the results
of a query. It's one of those functions that works perfectly for me in
development but randomly crashes in production. Thus far I've been
unable to reproduce the crash. The problem is surely in my code. And
before I dig
