Tom Lane t...@sss.pgh.pa.us writes:
[...]
Lastly, an atexit trigger will still fire during FATAL or PANIC aborts,
which scares me even more. When the house is already afire, it's
not prudent to politely let user-written perl code do whatever it wants
before you get the heck out of there.
Zdenek Kotala zdenek.kot...@sun.com writes:
[...]
+ header = (StandardChunkHeader *)
+ ((char *) ret - STANDARDCHUNKHEADERSIZE);
+
+// TRACE_POSTGRESQL_MCXT_ALLOC(context-name, context, size, header-size,
true);
+
[...]
If the dormant overhead of these probes is
Hi -
On Thu, Dec 10, 2009 at 09:33:28PM +0100, Zdenek Kotala wrote:
[...]
If the dormant overhead of these probes is measured or suspected to be
excessive, consider using the dtrace-generated per-probe foo_ENABLED()
conditional, or a postgres configuration global thusly:
[...]
Tom Lane t...@sss.pgh.pa.us writes:
[...]
See http://blog.endpoint.com/2009/05/postgresql-with-systemtap.html for
details. Perhaps it's worth noting in the documentation that SystemTap users
will need to use the double-underscore version?
I think a better solution is to persuade the
[EMAIL PROTECTED] (Tim Allen) writes:
: [...] Near the end he gets specifically asked about Red Hat
: Database as a competitive threat, and he responds that he doesn't
: think anyone can match their investment of 800 professionals to
: work on SQL Server. [...]
It would be naive to dismiss
tgl wrote:
: [...] (We have to physically fill each segment with zeroes to
: ensure that the system has actually allocated a whole 16MB to it;
: otherwise we fall victim to the hole-saving allocation technique
: of most Unix filesystems.) [...]
Could you explain how postgresql can fall
