I'm wondering if the mechanism used for sending signals between
postmaster processes on Win32 is much more heavyweight that is necessary.
Is there a reason not to call OpenThread on the target postmaster's
thread id, and then use QueueUserAPC to execute a 'signal handler'
method on it? (Or
Hi,
iam developing version control system based on content because i havent
found anything for postgres and it sounds like great tool to have.
Propably i will use Rules and Views with shadow tables, but iam
interested in alternative to examine WAL files.
So iam interested in WAL file format
Hi all,
While working on our network problems to send the full build result to
the buildfarm server, I just saw that a full buildfarm run with
-DCLOBBER_CACHE_ALWAYS option takes nearly 2 hours more than before
(from ~ 5h40 to 7h30).
This phenomenon has started with this run:
On Sun, 20 Apr 2008, Guillaume Smet wrote:
Date: Sun, 20 Apr 2008 16:23:47 +0200
From: Guillaume Smet [EMAIL PROTECTED]
To: pgsql-hackers list pgsql-hackers@postgresql.org, [EMAIL PROTECTED]
Subject: -DCLOBBER_CACHE_ALWAYS build takes far longer than before
Hi all,
While working on our
Guillaume Smet [EMAIL PROTECTED] writes:
While working on our network problems to send the full build result to
the buildfarm server, I just saw that a full buildfarm run with
-DCLOBBER_CACHE_ALWAYS option takes nearly 2 hours more than before
(from ~ 5h40 to 7h30).
It's probably due to the
On Sun, Apr 20, 2008 at 6:02 PM, Tom Lane [EMAIL PROTECTED] wrote:
It's probably due to the RANDOMIZE_ALLOCATED_MEMORY overhead added here:
pgsql/src/backend/utils/mmgr/aset.c 1.77
Right now that's on by default in assert-enabled builds. I'm not
sure if we want to leave it like that for
This is similar to a previous question I had asked about INSERT ...
DELETE ...
To be safe, to archive an existing row, and replace with a new row, I
believe on must do:
begin;
row := select ... from XXX where ... for update;
insert into XXX_archived values (row);
... update or
James Mansion wrote:
I'm wondering if the mechanism used for sending signals between
postmaster processes on Win32 is much more heavyweight that is
necessary.
Is there a reason not to call OpenThread on the target postmaster's
thread id, and then use QueueUserAPC to execute a 'signal
Alvaro Herrera wrote:
Magnus Hagander wrote:
Looking at the state of many of our non-english FAQs today, I don't
put too much faith into a system that'll just show people this is
not translated. I think it's more likely to get better if the
people can just edit the translations directly
Joshua D. Drake wrote:
Magnus Hagander wrote:
Alvaro Herrera wrote:
The FAQs are another matter however. I suggested some time back
moving those to DocBook XML. A friend was working on a script to
do the initial conversion automatically. The nice thing about it
is that we can then
See xlogdump and xlogviewer.
On Sun, Apr 20, 2008 at 7:44 AM, mito [EMAIL PROTECTED] wrote:
Hi,
iam developing version control system based on content because i havent
found anything for postgres and it sounds like great tool to have. Propably
i will use Rules and Views with shadow tables,
Is there any document describing WAL file format?
On Sun, Apr 20, 2008 at 7:20 PM, Jonah H. Harris [EMAIL PROTECTED]
wrote:
See xlogdump and xlogviewer.
On Sun, Apr 20, 2008 at 7:44 AM, mito [EMAIL PROTECTED] wrote:
Hi,
iam developing version control system based on content because i
:P
On Sun, Apr 20, 2008 at 5:14 PM, mito [EMAIL PROTECTED] wrote:
Hi,
iam developing version control system based on content because i havent
found anything for postgres and it sounds like great tool to have. Propably
i will use Rules and Views with shadow tables, but iam interested in
Peter Eisentraut wrote:
Mike Aubury wrote:
Am I missing something..
$ psql -q testdb
testdb=#
This also quiets out a few other unrelated things.
OK, I looked into the details of what the quiet mode does, and it turns out
that it does exactly what I want, including dropping a few other
On Saturday 19 April 2008 20:14, Joshua D. Drake wrote:
Tom Lane wrote:
I'm not against shortening the banner. What I'm against is turning this
thing into a camel (a horse designed by a committee). We should take
one approach or the other one, not both.
O.k. that makes sense. I have
xlog.c :)
On Sun, Apr 20, 2008 at 1:55 PM, Miloš Ország [EMAIL PROTECTED] wrote:
Is there any document describing WAL file format?
On Sun, Apr 20, 2008 at 7:20 PM, Jonah H. Harris [EMAIL PROTECTED]
wrote:
See xlogdump and xlogviewer.
On Sun, Apr 20, 2008 at 7:44 AM, mito
On Sun, 20 Apr 2008 14:25:36 -0400
Robert Treat [EMAIL PROTECTED] wrote:
Maybe we should add an additional paragraph to the psql welcome
message:
You can shorten or eliminate this welcome banner by modifying
your .psqlrc file and setting the WELCOME_MESSAGE to either terse
or none. For
What information are currently strored in WAL sequence ?
Jonah H. Harris wrote:
xlog.c :)
On Sun, Apr 20, 2008 at 1:55 PM, Miloš Ország [EMAIL PROTECTED] wrote:
Is there any document describing WAL file format?
On Sun, Apr 20, 2008 at 7:20 PM, Jonah H. Harris [EMAIL PROTECTED]
wrote:
We got the comment on the docs:
log_filename(string) is misleading, since it really doesn't use a
strftime pattern, but instead a reimplementation of strftime, in order
to be cross-platform. There is no documentation on this except to look
in src/timezone/strftime.c (the function is called
OK, I have spent some time generating and filtering typdefs via objdump
on various platforms. I filtered them and Bruce's list to eliminate
items not actually found in the sources thus:
while read line ; do grep -q -w -r --exclude=*.data --exclude=*.out
--exclude=*.sql --exclude=*.po
Joshua D. Drake [EMAIL PROTECTED] writes:
We got the comment on the docs:
log_filename(string) is misleading, since it really doesn't use a
strftime pattern, but instead a reimplementation of strftime, in order
to be cross-platform.
AFAIK that implementation covers everything that's in the
On Sun, 20 Apr 2008 21:32:53 -0400
Tom Lane [EMAIL PROTECTED] wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
We got the comment on the docs:
log_filename(string) is misleading, since it really doesn't use a
strftime pattern, but instead a reimplementation of strftime, in
order to be
Mark Mielke [EMAIL PROTECTED] writes:
# insert into product_image_archived select * from product_image where
itemno = 'XX' for update;
ERROR: cannot extract system attribute from virtual tuple
Hm, on an assert-enabled build this actually crashes :-(. It looks like
I broke the specific
Magnus Hagander wrote:
Yes. We used to use APCs, but touching anything remotely related to
Winsock from an APC is not supported... We had a lot of trouble with it
By implication you'd be doing socket'y stuff from the signal handler on
UNIX? Scary.
I was assuming it would be used to signal an
24 matches
Mail list logo
