Any Code::Blocks user? http://www.codeblocks.org/
Cannot compile PG-8.2.5 with WinXP SP2 using Code::Blocks.
I created a new project including ALL the files decompressed from
postgresql-8.2.5.tar.gz
and then just clicked on build. What's wrong?
Alternative ways to complie it with other IDE
On Wed, Nov 28, 2007 at 04:51:17PM +0100, Louis-David Mitterrand wrote:
On Wed, Nov 28, 2007 at 10:45:31AM -0500, Tom Lane wrote:
Louis-David Mitterrand [EMAIL PROTECTED] writes:
I am seeing this error with 8.3beta3 on debian unstable:
2007-11-28 15:15:46 CET ERROR: cached plan must
Josh Berkus wrote:
This might be worth mentioning, since it can be quite a big difference
in the right circumstances, and it helps a bit with the scalability
problem of the recovery. Should mention that it only helps with
full_pages_writes=on. One more reason to not gamble with data integrity
in puttuple_common(), the transition from an internal to external sort is
performed at the bottom of the TSS_INITIAL case in the main switch
statement.
The transition? Do we internal sort somewhere else and then external sort
here in tuplesort.c?
The function dumptuples() heapifies the
[EMAIL PROTECTED] writes:
The function dumptuples() heapifies the in-core tuples (divides the in-core
tuples into initial runs and then advances the state to TSS_BUILDRUNS).
Cannot see where dumptuples() advances the state to TSS_BUILDRUNS.
I expected something like
state-status =
Magnus Hagander wrote:
I did look at this at some earlier point as well. One big problem at that
time was that once you embedded mono, yuo had all sorts of threads running
in your backend ;-)
Is that necessarily a problem? You have to compile with a
thread-capable libc and take some
care
James Mansion wrote:
Magnus Hagander wrote:
I did look at this at some earlier point as well. One big problem at that
time was that once you embedded mono, yuo had all sorts of threads
running
in your backend ;-)
Is that necessarily a problem? You have to compile with a
thread-capable
[EMAIL PROTECTED] wrote:
Any Code::Blocks user? http://www.codeblocks.org/
Cannot compile PG-8.2.5 with WinXP SP2 using Code::Blocks.
I created a new project including ALL the files decompressed from
postgresql-8.2.5.tar.gz
and then just clicked on build. What's wrong?
Alternative ways to
Magnus Hagander [EMAIL PROTECTED] writes:
James Mansion wrote:
Is that necessarily a problem?
...
And yes, it would be the same as embedding Java. And it has been done
with pl/java, so it can be done :)
It is also pretty well established that if pltcl or plperl cause the
backend to become
Andrew Dunstan [EMAIL PROTECTED] writes:
The version I tested against is 5.8.8 - the latest stable release. The
5.8 series started in 2003 from what I can see - if anyone has a
sufficiently old system that they can test on 5.6.2 that will be useful.
I got around to trying it with a dusty
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tom Lane reports:
The version I tested against is 5.8.8 - the latest stable release. The
5.8 series started in 2003 from what I can see - if anyone has a
sufficiently old system that they can test on 5.6.2 that will be useful.
I got
I wrote:
I got around to trying it with a dusty 5.6.1 I have laying about on my
HPPA machine, and the news is not good: CREATE LANGUAGE plperl dumps
core deep inside libperl. With or without this patch.
As best I can tell at the moment, I have not tested 5.6.1 with anything
later than our
On Fri, 30 Nov 2007 06:32:10 -0500
Andrew Dunstan [EMAIL PROTECTED] wrote:
Simon Riggs wrote:
- Heap-Only Tuples (HOT) accelerate space reuse for UPDATEs
change to
Heap-Only Tuples (HOT) improve performance of frequent UPDATEs
I think we need to qualify this, or it could
Tom Lane [EMAIL PROTECTED] writes:
I think this can be fixed by changing the Executor so that it doesn't
use snapshot-curcid for this purpose. Instead, add a field to EState
showing the CommandID to mark tuples with. ExecutorStart, which has
enough information to know whether the query is
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
I think this can be fixed by changing the Executor so that it doesn't
use snapshot-curcid for this purpose. Instead, add a field to EState
showing the CommandID to mark tuples with. ExecutorStart, which has
enough
NikhilS [EMAIL PROTECTED] writes:
This can be handled by setting index-isconstraint appropriately inside
generateClonedIndexStmt().
Done.
The fundamental question though is should we allow primary, unique
CONSTRAINTS which use the index mechanism just as an implementation to be
created
Tom Lane wrote:
I wrote:
I got around to trying it with a dusty 5.6.1 I have laying about on my
HPPA machine, and the news is not good: CREATE LANGUAGE plperl dumps
core deep inside libperl. With or without this patch.
As best I can tell at the moment, I have not tested 5.6.1
Gregory Stark [EMAIL PROTECTED] writes:
ExecutorStart could also determine when the query is a write-only query for
which the provided command id won't be used for any snapshot checks (ie, a
simple INSERT) and tell CCI not to bump the CCI if the previous CC even if
it's dirty.
Ummm ... I'm
Hello
I have a stored procedure which does the billing stuff
in our system,it works ok,but if I put in
production,where there is some 5-10 billing events per
second,the whole database slows down. It won't even
drop some test table,reindex,vacuum,things which were
done before in the blink of an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/01/07 20:40, Dragan Zubac wrote:
Hello
I have a stored procedure which does the billing stuff
in our system,it works ok,but if I put in
production,where there is some 5-10 billing events per
second,the whole database slows down. It won't
Bruce Momjian [EMAIL PROTECTED] writes:
I need help understanding the following two release note items (see XXX):
I've tweaked the text for the first one. I do not think the second one
needs any changes; the matter is discussed elsewhere in the docs, and
the release notes are not the place to
On Sat, 1 Dec 2007, Tom Lane wrote:
I wrote:
I got around to trying it with a dusty 5.6.1 I have laying about on my
HPPA machine, and the news is not good: CREATE LANGUAGE plperl dumps
core deep inside libperl. With or without this patch.
As best I can tell at the moment, I have not tested
22 matches
Mail list logo
