Is it safe to call pfree() from multiple threads?
My Java backend will need to utilize finalizers. Objects like a saved
execution plan that has been forgotten must be released when the wrapping
Java object is finalized to avoid memory leaks. The finalizer is called from
the garbage collector
On Thursday 15 January 2004 21:48, Michael Brusser wrote:
I need to provide recommendations for optimal value for the
shared_buffers.
Any hints, or pointers to related reading would be very appreciated.
Mike.
First, read the annotated config file and performance guide here:
Just overheard one of my colleagues on the phone to one of our users
taking them through the process of moving their PGDATA to a partition
with space...
With the various paths, service names, config files and environment
variables PostgreSQL appears to have a multiple-personality
disorder... Is
Hi Lee
On Jan 16, 2004, at 8:09 PM, Lee Kindness wrote:
With the various paths, service names, config files and environment
variables PostgreSQL appears to have a multiple-personality
disorder... Is it:
postgresql (/etc/init.d/postgresql, postgresql.conf),
or postmaster (main postmaster
Thanks for the input Tom.
INMHO, this kind of statement should'nt cause any error even if the schema
doesn't exit *yet*; because:
1) if the script comes for pg_dump[all], we KNOW that this statement is
right
2) if it's typed in psql, and the user names the wrong schema, he will
find out very
I too was a little confused when starting out with PostgreSQL as to
what the difference was between some of these things, but they need
different names so people can distinguish between them.
You make a good point, and I think that's easier for developers to work
with.
However, why do
On Jan 16, 2004, at 9:39 PM, Jeff Davis wrote:
I can't point to any OSS project that completely renames its parts. I
think a shortened version of the name makes sense (in this case
postgres works well, but so does pgsql), and other projects do
similar things. Psql for the client and postmaster for
I can't be the only one forsee frustration from users who typo the set
search_path statement and then can't figure out why their tables aren't
showing up... can we emit a warning that not all of the schemas in the
search path were found?
Robert Treat
On Fri, 2004-01-16 at 06:47, [EMAIL
Joe Conway [EMAIL PROTECTED] writes:
Tom Lane wrote:
... That means that the contained fields had better not be
out-of-line TOAST value references, because there's no way to keep track
of them and keep from deleting the referenced value too soon.
Why wouldn't we handle this just like we do
Wouldn't it be a win for heap_tuple_toast_attrs() to fall out quickly
if the tuple contains no varlena attributes? I'm thinking of adding
a test like
/* Nothing to do if tuple contains no varlena fields */
if ((newtup !HeapTupleAllFixed(newtup)) ||
(oldtup
On Fri, 16 Jan 2004, Jeff Davis wrote:
I can't point to any OSS project that completely renames its parts. I
think a shortened version of the name makes sense (in this case
postgres works well, but so does pgsql), and other projects do
similar things. Psql for the client and postmaster for
On Fri, 16 Jan 2004, Michael Glaesemann wrote:
On Jan 16, 2004, at 9:39 PM, Jeff Davis wrote:
I can't point to any OSS project that completely renames its parts. I
think a shortened version of the name makes sense (in this case
postgres works well, but so does pgsql), and other projects
Thomas Hallgren [EMAIL PROTECTED] writes:
Is it safe to call pfree() from multiple threads?
There are no multiple threads in the backend, and no provision whatever
for thread safety. On anything, not only pfree. If your Java runtime
cannot be coerced into a single-thread mode of operation, you
Tom Lane wrote:
Wouldn't it be a win for heap_tuple_toast_attrs() to fall out quickly
if the tuple contains no varlena attributes? I'm thinking of adding
a test like
/* Nothing to do if tuple contains no varlena fields */
if ((newtup !HeapTupleAllFixed(newtup)) ||
From the Firebird FAQ:
The first beta was released on January 29, 2003. We are hoping to be
close to a full release some time around Easter 2003.
They are at RC8 right now ... running a *wee* bit behind scheduale :)
Marc G. Fournier Hub.Org Networking Services
Marc G. Fournier wrote:
On Fri, 16 Jan 2004, Michael Glaesemann wrote:
On Jan 16, 2004, at 9:39 PM, Jeff Davis wrote:
I can't point to any OSS project that completely renames its parts. I
think a shortened version of the name makes sense (in this case
postgres works well, but so does
On Fri, 16 Jan 2004, Thomas Swan wrote:
Perhaps postgresd, postgresqld, or pg_daemon might be a little more
intuitive?
I think at this late stage in the game (almost 10 years), changing could
be a bit difficult and confusing, no? :) I'd go with something like
pgsqld myself though, keeps it
Marc G. Fournier writes:
I think at this late stage in the game (almost 10 years), changing could
be a bit difficult and confusing, no? :) I'd go with something like
pgsqld myself though, keeps it short ... or we could go even shorter with
just pgd ...
But, I'm not, in any stretch
Marc G. Fournier wrote:
On Fri, 16 Jan 2004, Thomas Swan wrote:
Perhaps postgresd, postgresqld, or pg_daemon might be a little more
intuitive?
I think at this late stage in the game (almost 10 years), changing could
be a bit difficult and confusing, no? :) I'd go with something like
Is there a way to force database to load
a frequently-accessed table into cache and keep it there?
Thanks,
Mike.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Ok, That was what I suspected, but I was not 100% sure that it applied to
the memory allocation routines.
It has not escaped me that most things in the backend are indeed intended
for single-threading. I'm unaware of any way of coercing the Java runtime
into single threading. Instead, I took
Thomas Swan wrote:
I just thought the anecdote of confusing it for an MTA was a little funny.
Funny yes, but unfortunatly all too common for newbies I think.
---(end of broadcast)---
TIP 8: explain analyze is your friend
Michael Brusser [EMAIL PROTECTED] writes:
Is there a way to force database to load a frequently-accessed table
into cache and keep it there?
No.
BTW, this idea has been suggested in the past, so check the archives
for the prior discussions on this topic. The usual response is that
the
Marc G. Fournier [EMAIL PROTECTED] writes:
if you think about it, the postmaster is actually aptly named,
since it is the process that sorts out the incoming connections and
assigns them to backend processes ... just like the postmaster does
with your mail ...
Right, hence the witty pun :-)
On Fri, 16 Jan 2004, Michael Brusser wrote:
Is there a way to force database to load
a frequently-accessed table into cache and keep it there?
Nope. But there is a new cache buffer handler that may make it into 7.5
that would make that happen automagically.
---(end
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
Wouldn't it be a win for heap_tuple_toast_attrs() to fall out quickly
if the tuple contains no varlena attributes?
Why sure it would. That code is quite frequently called.
I take it back --- the short-circuit test already exists, but it's
It would be interesting to see the results if you do this test again with :
- scaling factor somewhere in the 100-300 range (so the generated db ~=
your ram amount)
- number of clients somewhere in 10-100
- number of transactions somewhere in 1000-1000
best wishes
Mark
P.s - Are you using the
Would it be doable, and would it be useful, to try to alternate the
directions of table and index scans every time each table/index was
fully scanned?
I was thinking that it could help cache performance at various levels
in cases where data at the end of a large table, say, that remained in
When replication is implemented, what is going to happen with database
systems that rely heavily on sequences for primary keys?
For example, consider this simple table:
CREATE SEQUENCE IntervalType_IntervalTypeID_seq start 1 increment 1
maxvalue 2147483647 minvalue 1 cache 1 ;
CREATE TABLE
Marc G. Fournier wrote:
From the Firebird FAQ:
The first beta was released on January 29, 2003. We are hoping to be
close to a full release some time around Easter 2003.
They are at RC8 right now ... running a *wee* bit behind scheduale :)
Yes, they're pretty late. Last time I read, the only major
30 matches
Mail list logo
