Thomas Hallgren wrote:
Luke Lonergan wrote:
Tom,
On 3/17/06 9:59 PM, Tom Lane [EMAIL PROTECTED] wrote:
This would buy what exactly?
I guess you didn't read the other 80% of the post.
In short, faster performance through more aggressive runtime
compilation. A
JIT for the database
Dave,
I wouldn't mind talking (or hosting a discussion) but have been unable to
think of anything that other hackers might be interested in. I obviously
can't discuss the server internals in any great depth, but if anyone wants
to hear about pgadmin, pginstaller, the web infrastructure or
Looking through the postgresql source code, I notice that there are many places
were palloc is used but the return value is not checked to see if it is null.
There are a few places such as:
if (!PointerIsValid(result = palloc(CASH_BUFSZ + 2 - count +
strlen(nsymbol
Mark Dilger wrote:
Looking through the postgresql source code, I notice that there are
many places were palloc is used but the return value is not checked
to see if it is null.
palloc will throw an exception if it cannot fulfill the request. Code
that checks the return value for null is in
Mark Dilger [EMAIL PROTECTED] writes:
Looking through the postgresql source code, I notice that there are many
places
were palloc is used but the return value is not checked to see if it is null.
Any place that *does* check it is incorrect (in the sense of being
wasted code space, not
Peter Eisentraut wrote:
Mark Dilger wrote:
Looking through the postgresql source code, I notice that there are
many places were palloc is used but the return value is not checked
to see if it is null.
palloc will throw an exception if it cannot fulfill the request. Code
that checks the
Mark Dilger wrote:
Peter Eisentraut wrote:
Mark Dilger wrote:
Looking through the postgresql source code, I notice that there are
many places were palloc is used but the return value is not checked
to see if it is null.
palloc will throw an exception if it cannot fulfill the request.
Alvaro Herrera wrote:
Mark Dilger wrote:
Peter Eisentraut wrote:
Mark Dilger wrote:
Looking through the postgresql source code, I notice that there are
many places were palloc is used but the return value is not checked
to see if it is null.
palloc will throw an exception if it
On Sun, 2006-03-19 at 17:14 -0500, Bruce Momjian wrote:
I see one in cash.c that I will remove.
I've already checked in a fix for that, as well as a few other places
that made similar mistakes -- sorry for stepping on your toes.
-Neil
---(end of
Hi,
On Sun, 2006-03-19 at 11:34 -0800, Josh Berkus wrote:
Well, aside from anything else, we seem likely to have you, Devrim,
Magnus and maybe even Robert Treat there (Robert?). Which would mean
a good time for a meeting of the Web Team, yes?
It seems that I'll be there, and yes, a
Mark Kirkwood wrote:
Tom Lane wrote:
I do notice a rather serious shortcoming of pg_freespacemap in its
current incarnation, which is that it *only* shows you the per-page free
space data, and not any of the information that would let you determine
what the FSM is doing to filter the raw
I wish someone will include --disable-indexes when copying/restoring
just like --disable-triggers
Thanks
Tom Lane [EMAIL PROTECTED] wrote
Hm, I already talked about that once:
http://www.postgresql.org/files/developer/transactions.pdf
but perhaps that's not the level of detail you are after?
Yeah, I've read the presentation -- and yes, that's not the level I am
after. Actually, I guess the
Josh,
Josh Berkus wrote:
I've heard a couple other requests for dealing with vaccuum. I think a
Fixing Vacuum Round-Table might be a valuable session if we have someone to
lead it. You ready?
If required. I want to know how people think about vacuum, and
many ideas around vacuum.
To be
Hello
I finished implementation dbms_pipe package for PostgreSQL. It fully support
private, public pipe, explicitly or implicitly created pipes, limits for
pipes. Please look:
http://pgfoundry.org/frs/download.php/818/orafce-2.0.0-preview.tgz
This version contains plvstr and plvdate
15 matches
Mail list logo
