On Sat, 2006-04-29 at 17:54 -0400, Tom Lane wrote:
> In some recent activity on the patches list about responding to bug #2073,
> http://archives.postgresql.org/pgsql-bugs/2005-11/msg00303.php
> we've been discussing various possible tweaks to the behavior of dropping
> or modifying a serial column
Currently, we disallow use of both FOR UPDATE and FOR SHARE in a single
query, as well as use of both NOWAIT and default "WAIT" semantics.
There is no reason for this except inadequately flexible data
representation, ie, a single flag for the whole Query instead of one per
target relation. I'm abo
On Sat, Apr 29, 2006 at 05:54:19PM -0400, Tom Lane wrote:
> In short, I think there's a reasonably good case to be made for losing the
> hidden dependency and re-adopting the viewpoint that saying SERIAL is
> *exactly* the same as making a sequence and then making a default
> expression that uses t
In some recent activity on the patches list about responding to bug #2073,
http://archives.postgresql.org/pgsql-bugs/2005-11/msg00303.php
we've been discussing various possible tweaks to the behavior of dropping
or modifying a serial column. The hacks involved with SERIAL seem to me
to be getting
> > Which brings me to the question - would it be reasonable to
> create a
> > .DEF file listing which symbols are exported from the
> postgres binary
> > to addon modules?
>
> No, I'd not think this is a good idea. Unlike libpq, there's
> no clear demarcation of an intended API, and no real
Thanks, but from the vail site "windows sorry"... I am working in windows. I was thinking in a simply implementation, with only global variables used with the rule system. I can write the c code for this.Tom Lane <[EMAIL PROTECTED]> wrote: Juan Manuel Diaz Lara <[EMAIL PROTECTED]>writes:>
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Which brings me to the question - would it be reasonable to create a
> .DEF file listing which symbols are exported from the postgres binary to
> addon modules?
No, I'd not think this is a good idea. Unlike libpq, there's no clear
demarcation of an
Juan Manuel Diaz Lara <[EMAIL PROTECTED]> writes:
> I would like to implement a row-level security for
> application-level-user (the user is not a postgresql user),
Have you looked at Veil?
http://veil.projects.postgresql.org/
regards, tom lane
---
I would like to implement a row-level security for application-level-user (the user is not a postgresql user), I wish to restrict access to rows in diferent tables based on this application-level-user. My idea is to use rules to rewrite queries based on the contents of a global variable that is set
Should we make the whole postgres logging system configurable, similar to log4j
(or log4perl) rather than special-casing the autovacuum logs? Do we want to see
options added piecemeal to the conf file such as "autovacuum_messages=silent"?
mark
---(end of broadcast)---
-Original Message-
From: "Thomas Hallgren"<[EMAIL PROTECTED]>
Sent: 29/04/06 14:43:09
To: "PostgreSQL-development"
Subject: [HACKERS] stdout when running as a Windows service
> I'm having problems with crashes whenever I attempt to write something
> on stdout or stderr from a UDT whenev
Kris Jurka wrote:
On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
Kris Jurka wrote:
Anyway the test exits with
Stuck spinlock (80618e9) detected at ./s_lock.c:355.
on a linux gcc build this exits with
Stuck spinlock (0x5013ad) detected at ./s_lock.c:402.
This seems like a different probl
Kris Jurka wrote:
On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
What platform is that? (OS rev, architecture and word size)? I
tested the changes I submitted on Solaris 10 amd64.
$ uname -a
SunOS albert 5.9 Generic_112234-03 i86pc i386 i86pc
$ cc -V
cc: Sun WorkShop 6 update 2 C 5.3 Pat
Kris Jurka wrote:
On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
The file that uses the spinlocks:
/src/backend/storage/lmgr/s_lock.c
can be compiled standalone with -DS_LOCK_TEST
To get the test to compile I had to link in tas.o as the attached
patch shows. Unfortunately this doesn't w
Bruce Momjian wrote:
Kris Jurka wrote:
Bruce Momjian wrote:
Log Message:
---
Modify Solaris compiler build rules to use the cpp preprocessor, the the
x86 file.
Well it compiles now, but it doesn't seem to work:
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=kudu&dt=200
I'm having problems with crashes whenever I attempt to write something
on stdout or stderr from a UDT whenever the postmaster is running as a
windows service. Not sure what I'm doing wrong. Is this a known problem?
Regards,
Thomas Hallgren
---(end of broadcast)
Theo Schlossnagle wrote:
> Kris Jurka wrote:
>
> >
> >
> > On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
> >
> >> Kris Jurka wrote:
> >>
> >>> Anyway the test exits with
> >>> Stuck spinlock (80618e9) detected at ./s_lock.c:355.
> >>>
> >>> on a linux gcc build this exits with
> >>> Stuck spinlock
On Sat, Apr 29, 2006 at 10:56:20AM +0200, Magnus Hagander wrote:
> While working on the VC++ build, I initially (accidentally) built
> postgres.exe witohut exporting all symbols (because VC++ doesn't have a
> builtin functionality to do export-all). When enabling it to export all,
> I noticed the b
While working on the VC++ build, I initially (accidentally) built
postgres.exe witohut exporting all symbols (because VC++ doesn't have a
builtin functionality to do export-all). When enabling it to export all,
I noticed the binary increased more than 30% in size, and the linker
time increased arou
19 matches
Mail list logo
