query times will grow with table size, and that partitioning,
combined with parallel query execution can address that problem. I'm more
wondering about problems in maintaining tables and indexes once we have
10B, 20B, ... rows.
Jack Orenstein
for the
btree index to subsume GIN index capabilities?
Jack Orenstein
rect, and that the PG_RETURN_POINTER statement is
being reached.
I have been reading the Postgres docs, and comparing my code to the
examples in contrib, and cannot see what I'm doing wrong. Can anyone see a
problem in what I've described? Or point me in the right direction to debug
this problem?
Thanks.
Jack Orenstein
Thank you, the missing STORAGE clause was the problem.
As for the non-standard coding: I did start out with more correct coding,
and it wandered off as I tried to figure out what was causing the crash.
Jack Orenstein
On Sun, Jan 3, 2021 at 7:57 PM Tom Lane wrote:
> Jack Orenstein wri
appears to be involved in
programming language extensions, and the function is declared in plpgsql.h.
Looking at various contrib modules, I see
explicit declarations of _PG_init(void).
Should _PG_init(void) be declared in someplace included by postgres.h or
fmgr.h?
Jack Orenstein
atype, but this crash occurs
without the index.)
I'm interested in advice on how to go about hunting down my problem.
Something along the lines of a debugging malloc, or valgrind, for Postgres.
Jack Orenstein
gy. Can
someone clarify my confusion, and perhaps point me at a tutorial on correct
usage of the interfaces for LWLocks and shared memory, (I haven't been able
to find one).
Thank you.
Jack Orenstein
works must be way off. Is there a
presentation or paper that explains how GIN works?
Jack Orenstein
On Sat, Jan 9, 2021 at 12:18 PM Tom Lane wrote:
> Jack Orenstein writes:
> > I am writing a Postgres extension, and thought that I had memory
> > corruption, (thanks for the --enable-cassert lead). I might, but It now
> > looks like I need to understand the use of shar
