2009/7/4 Greg Stark :
> On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark wrote:
>> It's pretty hard to guess where your bug is sitting here with no code
>> and no idea even what you've done to trigger it.
>>
>> At a guess there someplace you haven't detoasted a datum that had to
>> be detoasted. But lik
2009/7/4 Greg Stark :
> On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark wrote:
>> It's pretty hard to guess where your bug is sitting here with no code
>> and no idea even what you've done to trigger it.
>>
see attachment - sorry, comments are czech
>> At a guess there someplace you haven't detoasted
On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark wrote:
> It's pretty hard to guess where your bug is sitting here with no code
> and no idea even what you've done to trigger it.
>
> At a guess there someplace you haven't detoasted a datum that had to
> be detoasted. But like I said that's just a guess.
It's pretty hard to guess where your bug is sitting here with no code
and no idea even what you've done to trigger it.
At a guess there someplace you haven't detoasted a datum that had to
be detoasted. But like I said that's just a guess.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
Hello,
I can't to find reason of my problem. I have a varlena type. This type
works well with plain storage, but this raise some random exception
with extended storage. It finish on Assert((data - start) ==
data_size)[heaptuple.c]; I checked - when I return varlena from in
function, then it has co
