Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have cleaned up the contrib install/uninstall to be more consistent,
> > used CREATE OR REPLACE function consisently, and removed transaction
> > blocks.
>
> ... and broken the buildfarm ...
OK, fixed, thanks.
--
Bruce Momjian
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have cleaned up the contrib install/uninstall to be more consistent,
> used CREATE OR REPLACE function consisently, and removed transaction
> blocks.
... and broken the buildfarm ...
regards, tom lane
-
Bruce Momjian wrote:
> Tom Lane wrote:
> > "Marko Kreen" <[EMAIL PROTECTED]> writes:
> > > On 11/10/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > >> OK, first question. How would someone have the 8.0 signatures in 8.2?
> > >> Don't they reinstall pgcrypto for every major release?
> >
> > > Why
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> If you don't re-run a contrib module's sql script then you don't get any
> >> new functions that may have been added to the module. So I think the
> >> real issue here is that we ought to deprecate the idea of ski
In this thread:
http://archives.postgresql.org/pgsql-sql/2007-11/msg00038.php
we saw that there is considerable new potential for user confusion
created by the 8.3 extensions to allow any type name to be decorated
with typmod parameters (which can be either constants or identifiers).
I see no probl
I've seen several comments about shared memory under Windows being
"slow", but I haven't had much luck finding info in the archives.
What are the details of this? How was it determined and is there a
straightforward test/benchmark?
---(end of broadcast)---
On 10/26/07, I wrote:
> On 10/26/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> > Can you try the attached patch? See how many backends you can get up to.
> >
> > This patch changes from using a single thread for each backend started to
> > using the builtin threadpool functionality. It also re
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> Not quite --- it's just "returns setof record".
> I did test my example before posting it:
> postgres=# postgres=# CREATE or replace FUNCTION getfoo (IN int, OUT int, OUT
> int) returns setof record(int,int)AS
Abhijit Menon-Sen <[EMAIL PROTECTED]> writes:
> The server logs "WARNING: nonstandard use of \\ in a string literal at
> character 44", but the message comes with sqlstate code 22P06, which is
> in an error class ("Data exception"). So my application thinks it's an
> error, and is unhappy.
If you
Just a small thought. If the file decision is preferred, then it might
be worth considering to create a file per tablespace.
Thanks,
Gokul.
On Nov 9, 2007 7:15 PM, Simon Riggs <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-11-09 at 13:27 +, Heikki Linnakangas wrote:
> > Alvaro Herrera wrote:
> >
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I'm evaluating the option of write a PG-extension which allow the
> application to apply some per-connection filters. This filters work at
> table level and remove records which aren't allowed from a select
> result-set.
It sounds a whole lot li
Bruce Momjian <[EMAIL PROTECTED]> writes:
> However, I am still unclear if the dump code is correct because I don't
> see the backslash preserved in \\'' cases, just cases:
> test=> INSERT INTO Foo(bar) VALUES (E'\\''x');
You're just confused. That produces a word whose contents are t
Hi Tom,
At 02:51 10/11/2007, Tom Lane wrote:
Uh, no, it's called only when we've advanced datfrozenxid,
which is a pretty uncommon event. So I think the real hole in the
proposal is that there would be a long and not-very-predictable delay
between changing the parameter and having it really tak
On Nov 8, 2007, at 10:46 , Andrew Dunstan wrote:
Tom Lane wrote:
Michael Glaesemann <[EMAIL PROTECTED]> writes:
What would be the disadvantages of always doing this, i.e., just
making this part of the normal update path in the backend?
(1) cycles wasted to no purpose in the vast majo
The server logs "WARNING: nonstandard use of \\ in a string literal at
character 44", but the message comes with sqlstate code 22P06, which is
in an error class ("Data exception"). So my application thinks it's an
error, and is unhappy.
Since the sqlstate code is the only useful machine-readable f
15 matches
Mail list logo
