Ok, I got it, google is my friend ;)
...
> Can I use valgrind to find out the root of problem. If so, how should I
> invoke it with postgres. Postgres it self was configured with:
...
--
GJ
Binary system, you're either 1 or 0...
dead or alive ;)
---(end of broadcast)
On Wednesday 26 October 2005 18:34, Oleg Bartunov wrote:
> btw, if you could read russian, we have GiST programming tutorial
> http://www.sai.msu.su/~megera/postgres/talks/gist_tutorial.html
I did try, but last time I did Russian lessons was around 10 years ago, so ...
babel fish could help btw, bu
btw, if you could read russian, we have GiST programming tutorial
http://www.sai.msu.su/~megera/postgres/talks/gist_tutorial.html
Oleg
On Wed, 26 Oct 2005, Tom Lane wrote:
Grzegorz Jaskiewicz <[EMAIL PROTECTED]> writes:
I created custom type, and attempt to create gist indexing for it,
On Wednesday 26 October 2005 17:48, Tom Lane wrote:
> Looks like you're scribbling on memory that doesn't belong to you.
> Check for miscomputed palloc request sizes, etc.
Thanks very much for the tip. I thogut perhaps I am not filling out some parts
of structures, or something.
Can I use valgrind
Grzegorz Jaskiewicz <[EMAIL PROTECTED]> writes:
> I created custom type, and attempt to create gist indexing for it, to
> make search wind quick.
> on select from * where something << 'something'; I get:
> WARNING: problem in alloc set GiST temporary context: detected write
> past chunk end i
