Matthew T. O'Connor wrote:
Tom Lane wrote:
ROTFL ... so to translate: If your program crashes, please release
locks before crashing.
Obviously that wasn't the intent of the above, but I guess it is the net
effect. Either way, I don't think it's a huge problem, it just means
that PG may
Pavel Stehule wrote:
2008/6/4 David E. Wheeler [EMAIL PROTECTED]:
Exactly. The issue is that application developers, who are not DBAs, have no
idea how to tune PostgreSQL, and postgresql.conf is daunting and confusing.
So they use a different database that's faster.
do you thing, so any
Magnus Hagander wrote:
For the record, what we were talking about was snapshotting the time at
backend start and then use QueryPerformanceCounter() to see what
happened and do some calculation.
Although this might not be such a big issue for the regression tests:
Be aware that the reliability of
Greg Smith wrote:
Was working on some documentation today and I realized that I've taken for
granted the lore about not using large values for shared_buffers in
Windows without ever understanding why. Can someone explain what the
underlying mechanism that causes that limitation is? From
Gregory Stark wrote:
This is because of (at least) two changes in the ABI between the runtimes used
by mingw and VC++.
1) Enums are apparently 8 bytes on VC++ but 4 bytes on mingw
They are 4 bytes here on my 32 bit WinXP machine with VS2005SP1.
2) time_t is 8 bytes on VC++ but 4 bytes on
Gregory Stark wrote:
The looming problem is that you won't be able to use any libraries or 3rd
party tools which use time_t in their interface unless you build with the same
size time_t as they do. I don't know how're expected to find out that a .so
you're handed has a different size time_t.
But
Markus Schiltknecht wrote:
[2]: Terms and Definitions of Database Replication
http://www.postgres-r.org/documentation/terms
Markus, the links in the left side menu are broken on the about and
documentation page. They point to http://www.postgres-r.org/overview
instead of
