Re: Threaded PosgreSQL server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mkscott(at)sacadia(dot)com
Cc: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, mlw <markw(at)mohawksoft(dot)com>, Justin Clift <justin(at)postgresql(dot)org>, Haroldo Stenger <hstenger(at)adinet(dot)com(dot)uy>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: Threaded PosgreSQL server
Date: 2002-02-08 16:17:51
Message-ID: 23872.1013185071@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

<mkscott(at)sacadia(dot)com> writes:
> I can definitely take a stab aat it. Maybe I can make a test case with
> some globals that are accessed often submit some patches to see what
> people think. Can I send them to you?

I have a sneaking feeling that what you are going to come up with is a
multi-megabyte patch to convert CurrentMemoryContext into a non-global,
which will require changing the parameter list of damn near every
routine in the backend.

Personally I will vote for rejecting such a patch, as it will uglify the
code (and break nearly all existing user-written extension functions)
far more than is justified by what it accomplishes: exactly zero, in
terms of near-term usefulness.

I think what's more interesting to discuss at this stage is the
considerations I alluded to before: what are we going to do with the
caches and other potentially-sharable datastructures? Without a
credible design for those issues, there is no point in sweating the
small-but-annoying stuff.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren Johnson 2002-02-08 16:23:13 Re: Replication
Previous Message Matthew T. O'Connor 2002-02-08 16:17:29 Re: Why dump/restore to upgrade?