I'm looking for ways to make the patch simpler and less invasive.
Any objections to changing the name of RedirectDead? A RedirectDead
ItemId is not really redirected, it's just a stub representing a dead
tuple (the space for that tuple has been reused but an index entry may
still point to the
Not that I think that anyone owning both a law degree and a computer
in 2007 should legitimately be able to plead innocence here. FAST
Australia's lawyers are making themselves look like idiots, and the
same for every other company tacking on such notices. I think the
real bottom line
Applied.
Thanks for your help Bruce (and Tom and Nikhil).
-- Korry
Patch applied. Thanks. I did not backpatch this to 8.2.X. If I
should, let me know.
Thanks Bruce - this bug will prevent plugins (like the PL/pgSQL debugger,
profiler, and tracer) from working on Windows hosts, so I think it would be
useful to backpatch to 8.2.
-- Korry
[EMAIL PROTECTED] wrote:
Patch applied. Thanks. I did not backpatch this to 8.2.X. If I
should, let me know.
Thanks Bruce - this bug will prevent plugins (like the PL/pgSQL
debugger, profiler, and tracer) from working on Windows hosts, so I
think it would be useful to
Right - but LINUX_PROFILE was added to correct Linux specific oddities
with the time counter accumulation, whereas your patch is not Linux
specific at all. So I think a more representative symbol is required.
Yeah, that was my problem with the patch too. The issue that it's
addressing
It's difficult to profile a backend server process (using gprof)
because each process overwrites any earlier profile as it exits.
It is especially tricky to nab a useful profile if you happen to have
autovacuum enabled.
This patch reduces the problem by forcing the backend to 'cd' to a new
This patch fixes shared_preload_libraries on Windows hosts. It forces
ach backend to re-load all shared_preload_libraries.
(see http://archives.postgresql.org/pgsql-hackers/2007-01/msg01498.php
for discussion)
-- Korry
--
Korry Douglas[EMAIL PROTECTED]
EnterpriseDB
s/XMLGEN/XMLAGG/
Sorry, I meant XMLAGG() not XMLGEN()
And now that I have the name right, I found the answer:
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01022.php
Sorry to be a bother...
-- Korry
Here is an updated updated XML patch. Unless there are objections of
the sort that this approach is totally wrong or there is crash
potential, I'd like to get this committed this week and fill in the
gaps next year.
Peter - I have a few quick questions about the XML patch that you
s/XMLGEN/XMLAGG/
Sorry, I meant XMLAGG() not XMLGEN()
-- Korry
Here is an updated updated XML patch. Unless there are objections of
the sort that this approach is totally wrong or there is crash
potential, I'd like to get this committed this week and fill in the
gaps
11 matches
Mail list logo
