>>> On Thu, Dec 27, 2007 at 4:22 PM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
> To the extent that you do believe the spec, there are more problems with
> our precedence rules than just where <= fits --- it looks to me lik
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> That said, bringing PostgreSQL into compliance with the standard
> would undoubtedly break some people's existing applications.
The spec seems to barely have a notion of operator precedence at all ---
for example, all the variants of are at the same
>>> On Mon, Dec 17, 2007 at 1:58 PM, in message
<[EMAIL PROTECTED]>, "Pedro Gimeno"
<[EMAIL PROTECTED]> wrote:
> Description:Nonstandard precedence for comparison operators
> The operators <>, <= and >= are expected to have the same precedence as =, <
> and >, but according to the doc
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Can we throw some more specific SQLSTATE than the default "internal
>> error" here?
> Hmm. I looked at the extant list, and found that the contrib/xml2 code
> uses ERRCODE_EXTERNAL_ROUTINE_EXCEPTION whereas pgcrypto uses
> ERRCODE_EX
On Thu, 2007-12-27 at 10:10 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > If there are no objections, I will add an extra condition to the wait,
>
> That's not the correct fix. The problem is that the archiver is getting
> killed in the first place. What the postmaster sho
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > if (err != NULL)
> > ereport(ERROR,
> > (errmsg("OSSP uuid failure: %s", err)));
> > else
> > ereport(ERROR,
> > (errmsg("OSSP uuid failure: error code %d", rc)));
>
> Maybe "OS
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> if (err != NULL)
> ereport(ERROR,
> (errmsg("OSSP uuid failure: %s", err)));
> else
> ereport(ERROR,
> (errmsg("OSSP uuid failure: error code %d", rc)));
Maybe "OSSP uuid library failure"? Otherwi
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Please try the attached patch.
>
> Most of the invocations of pguuid_complain will be outright lies as to
> which function is complaining. Please rethink the error message.
Doh! Sorry. How about this:
static void
pguuid_complain
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I think this makes plenty of sense. However, something that occured to
> > me just now is that perhaps the right thing to do in the long term is to
> > put this message in errcontext and leave the "invalid value for XXX" as
> > the m
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I think this makes plenty of sense. However, something that occured to
> me just now is that perhaps the right thing to do in the long term is to
> put this message in errcontext and leave the "invalid value for XXX" as
> the main error message. That w
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Please try the attached patch.
Most of the invocations of pguuid_complain will be outright lies as to
which function is complaining. Please rethink the error message.
regards, tom lane
---(end of broadc
Simon Riggs <[EMAIL PROTECTED]> writes:
> If there are no objections, I will add an extra condition to the wait,
That's not the correct fix. The problem is that the archiver is getting
killed in the first place. What the postmaster should do instead is
waken it after the shutdown process termina
I have a service that was installed on my pc with the postgres service.
We went in and had to change the password to match our domain policies
and now ever time we reboot it re-writes the password to something else
on the service and we have to change it under logon as,
Any thoughts?
Alvaro Herrera wrote:
> Dmitriy wrote:
>
> > in sql console:
> > postgres=# select uuid_nil();
> > server closed the connection unexpectedly
> > This probably means the server terminated abnormally
> > before or while processing the request.
>
> Thanks for the report. I think the proble
Dmitriy wrote:
> in sql console:
> postgres=# select uuid_nil();
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
Thanks for the report. I think the problem here is that we're not
checking th
sivaprakash escribió:
> Operating system: windows 2003 server
>
> In TASK MANAGER postgres service should showed in 30 times
This is normal. Four (or five) of those are base server processes, and
the others correspond to one process per connection.
--
Alvaro Herrera
Tom Lane wrote:
> That's getting to be a bit complicated to replicate in N places, though.
> Plus if we ever want to make it work like Alvaro is thinking of, we'd
> have to go back and change all those places again. So I propose
> inventing a function
>
> int guc_complaint_level(GucSource
On Thu, 2007-12-27 at 09:41 +, [EMAIL PROTECTED] wrote:
> The following bug has been logged online:
>
> Bug reference: 3843
> Logged by:
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3beta4
> Operating system: RHEL5
> Description:archiver process is r
The following bug has been logged online:
Bug reference: 3843
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta4
Operating system: RHEL5
Description:archiver process is restarted after the smart shutdown
Details:
Is this a bug though archiver
On Thu, Dec 27, 2007 at 08:02:24AM +, sivaprakash wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3842
> Logged by: sivaprakash
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8,1
> Operating system: windows 2003 server
> Description:
The following bug has been logged online:
Bug reference: 3842
Logged by: sivaprakash
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8,1
Operating system: windows 2003 server
Description:Service
Details:
In TASK MANAGER postgres service should showed in 30 time
The following bug has been logged online:
Bug reference: 3841
Logged by: Dmitriy
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.beta4
Operating system: FreeBSD 6.2-RELEASE
Description:core dump in uuid-ossp
Details:
in sql console:
postgres=# select uuid_
22 matches
Mail list logo
