hello,
i've attached a patch for the following bug
report:
http://archives.postgresql.org/pgsql-ports/2004-09/msg8.php
in essence, if configure detects that the
environment is sunos4, s_lock.c should use the
.seg opcode. otherwise, s_lock.c should use
.section.
i've tested this
Greetings,
Small patch to move get_grosysid() from catalog/aclchk.c to
utils/cache/lsyscache.c where it can be used by other things. Also
cleans up both get_usesysid() and get_grosysid() a bit. This is in
preparation for 'Group Ownership' support.
Thanks,
Stephen Frost [EMAIL PROTECTED] writes:
Small patch to clean up the grammer a bit by adding 'GroupId',
'SchemaName' and 'SavePointId'.
I don't particularly see the value of this --- especially since the
direction of future development is likely to be to remove the
distinction between user
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
Small patch to clean up the grammer a bit by adding 'GroupId',
'SchemaName' and 'SavePointId'.
I don't particularly see the value of this --- especially since the
direction of future development is likely to
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
Do you agree with the other changes (ColId - SchemaName, ColId -=20
SavePointId) ?
I don't really see the value of them. They add some marginal
documentation I suppose, but they also make the grammar bigger and
Stephen Frost [EMAIL PROTECTED] writes:
Personally, I'd just like it to be
consistent, when I was looking at how to add the grammar for group
ownership group names were identified in one place as 'ColId' and another
as 'UserId', iirc.
Oh, I had forgotten we already had a UserId production.
* Tom Lane ([EMAIL PROTECTED]) wrote:
Given other discussion, it might be best to rename it to RoleId and use
that for both users and groups.
Ok, should I change SchemaName SavePointId back to ColId, leave them
as in the patch, change them to RoleId, or something else? Neither
ColId nor
Stephen Frost [EMAIL PROTECTED] writes:
Ok, should I change SchemaName SavePointId back to ColId,
I'd just leave them as ColId. I don't think much would be gained by
introducing those productions.
regards, tom lane
---(end of
* Tom Lane ([EMAIL PROTECTED]) wrote:
Stephen Frost [EMAIL PROTECTED] writes:
Ok, should I change SchemaName SavePointId back to ColId,
I'd just leave them as ColId. I don't think much would be gained by
introducing those productions.
Done, here's the patch.
Thanks,
Folks,
We have implemented SELECT FOR UPDATE NOWAIT for PostgreSQL.
The patch attached to this email contains all the required code
including ECPG updates and some documentation.
It would be nice if this patch would be included in PostgreSQL 8.1
Best regards,
Ewald
On Mon, Dec 27, 2004 at 01:03:08PM -0500, Kris Jurka wrote:
has not prepared. So I don't see why, simply because it's in a pool, that
it forgets what's been prepared.
The connection (the open socket to Postgres) doesn't forget anything. If
you have multiple machines sharing a connection pool,
[EMAIL PROTECTED] writes:
in essence, if configure detects that the
environment is sunos4, s_lock.c should use the
.seg opcode. otherwise, s_lock.c should use
.section.
i've tested this and i've gotten the latest CVS
source to compile under Solaris 9 using sun's
compiler.
Applied, except
12 matches
Mail list logo
