Marc G. Fournier schrieb:
Just as a heads up, I'm going to roll it in about 4hrs (~02:00GMT) ...
I checked a couple of mirrors this morning and only the swedish one got
it so far. (timestamps 03:24 - 03:36)
Maybe it would be better next time to upload it before 0:00 GMT
--
Reini Urban
http://xarch
Check her out and let me know if there are any problems ... I've changed
the mk script to pull in the beta3 man pages that I found in the dev/doc
directory ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy
On Sat, 2004-11-20 at 16:14, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Thu, 2004-11-18 at 22:55, Tom Lane wrote:
> >> If it is a problem, the LockBuffer calls in RelationGetBufferForTuple
> >> would be the places showing contention delays.
>
> > You say this as if we can eas
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Just as a heads up, I'm going to roll it in about 4hrs (~02:00GMT) ...
>
> Works for me. I've got two small patches I'm about to commit, and then
> I'll go update the release notes; should be done in an hour or two.
Fine by me.
Tom Lane wrote:
... I would like to prevent the commands "begin [work or
transaction]", "commit", and "rollback", completely
If you are executing through SPI then those operations are disallowed
already.
Ah, yes I had forgotten that. One problem less to solve.
The main problem with this propo
James William Pye wrote:
Although, I'm inclined to think that if you require this sort of
flexibility you should probably think about writing your own SPI.
I think it's far better if we all focus our efforts to improve on the
PostgreSQL SPI. That way, all PL's will benefit. That's the reason I
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Just as a heads up, I'm going to roll it in about 4hrs (~02:00GMT) ...
Works for me. I've got two small patches I'm about to commit, and then
I'll go update the release notes; should be done in an hour or two.
regards, tom
Just as a heads up, I'm going to roll it in about 4hrs (~02:00GMT) ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
---(end of broadcast)
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I don't currently have the resources to clean this up properly. The
> attached patch tries to make clear in a comment what the code is doing,
> and also initializes these variables to NULL. If someone wants to take a
> stab at cleaning this up they ar
On Sun, 2004-11-21 at 16:55 +0100, Thomas Hallgren wrote:
> In a PL language it's sometimes desirable to prevent execution of some
> commands. I would like to prevent the commands "begin [work or
> transaction]", "commit", and "rollback", completely and I would like to
> force the user to use e
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> In a PL language it's sometimes desirable to prevent execution of some
> commands. I would like to prevent the commands "begin [work or
> transaction]", "commit", and "rollback", completely and I would like to
> force the user to use explicit method
On Wednesday 17 November 2004 20:39, Arman Bostani wrote:
> I was wondering if there's a bug/issue tracking system for pgsql? (e.g.
> something like http://www.bugzilla.org) Is the TODO list all that there
> is?
>
There is no bugzilla interface, though it has been discussed in the past.
Current
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> I guess my concern is that on Sparc64/OpenBSD-3.6* at least, this bug is
> exposed by the seg tests but might well occur elsewhere and bite us in
> various unpleasant ways.
The experimentation I did to develop the test case suggested that the
problem
Hi,
Environment:
SunOS 5.7 Generic_106541-29 sun4u sparc SUNW,UltraSPARC-IIi-Engine
Postgresql-7.4.6
Build config: --with-java --enable-thread-safety
gcc version 3.3.1
less-381
readline-4.3
$ echo $PAGER
/usr/local/bin/less
$ echo $LESS
-e
I recently
Joe Conway wrote:
Along those lines, this is what I've been using in PL/R:
#if (CATALOG_VERSION_NO <= 200211021)
#define PG_VERSION_73_COMPAT
#elif (CATALOG_VERSION_NO <= 200310211)
#define PG_VERSION_74_COMPAT
#else
#define PG_VERSION_80_COMPAT
#endif
I wasn't following this thread earlier, but if
In a PL language it's sometimes desirable to prevent execution of some
commands. I would like to prevent the commands "begin [work or
transaction]", "commit", and "rollback", completely and I would like to
force the user to use explicit methods for the savepoint methods.
I wonder if there's an
Neil Conway wrote:
Ruey-Lung Hsiao wrote:
My problem is: I can't find a way to compare strings in C
preprocessor directive since PG_VERSION is defined as something like
"7.4.3" or "7.4.6".
You could try using CATALOG_VERSION_NO in src/include/catversion.h as a
substitute for the version number
Stefan Kaltenbrunner said:
> Tom Lane wrote:
>> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>>
>>>Meanwhile, what do we do? Turn off -O in src/template/openbsd for
>>>some/all releases?
>>
>>
>> Certainly not. This problem is only known to exist in one gcc version
>> for one architecture, and besid
3 times lucky?
Last one broke utf8 G
This one works, Too tired, sorry for the inconvenience..
... John
cvs.diff
Description: cvs.diff
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Meanwhile, what do we do? Turn off -O in src/template/openbsd for
some/all releases?
Certainly not. This problem is only known to exist in one gcc version
for one architecture, and besides it's only affecting (so far as we can
tell) one
Thomas Hallgren wrote
I'm planning to add subtransactions too, but my approach will be to
use the savepoint functionality already present in the
java.sql.Connection interface. Perhaps the plpy implementation could
do something similar. This is what I'm planning to implement:
In Java, safepoints
Ruey-Lung Hsiao wrote:
My problem is: I can't find a way to compare strings in C preprocessor
directive since PG_VERSION is defined as something like "7.4.3" or
"7.4.6".
You could try using CATALOG_VERSION_NO in src/include/catversion.h as a
substitute for the version number.
I think it would
Tom Lane wrote:
James William Pye <[EMAIL PROTECTED]> writes:
I have been playing with RollbackToSavepoint and ReleaseSavepoint, but
per Neil's comments on IRC and the fact that I have to annoyingly
construct a List containing the savepoint name. I get the feeling that I
am not meant to use them.
On Sat, 2004-11-20 at 19:56, Joe Conway wrote:
> When returning "setof record", the column definition must exist in the
> query, and must match what ultimately is returned. This means that
> whatever logic you use in your application to write the sql statement
> must be able to derive the appro
Updated patch, Disregard old one, it broke ucs2.
... John
cvs.diff
Description: cvs.diff
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that
Ruey-Lung Hsiao <[EMAIL PROTECTED]> writes:
> In my X_in() function, I want to access other table to do some
> bookkeeping stuff. this table keeps track of the number of calls to
> X_in(). However, while SPI_connect() returns SPI_OK_CONNECT, whenever I
> execute SPI_exec( "SELECT count FROM XTAB
Tom Lane wrote:
There's an ancient saying "I can make this code arbitrarily fast ...
if it doesn't have to give the right answer". I think that applies
here. Fast and unsafe is not how the Postgres project customarily
designs things.
I'm missing something, that's clear. Because I can't see why th
Ruey-Lung Hsiao <[EMAIL PROTECTED]> writes:
>My question is: how do I find or define ordering operators for my
> user-defined type?
Create a default btree index operator class for the type. See
http://developer.postgresql.org/docs/postgres/xindex.html
regards, tom la
28 matches
Mail list logo
