> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 29 August 2005 21:32
> To: Magnus Hagander
> Cc: Dave Page; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] CVS Head: Pg_ctl bug?
>
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > Though I don't see any of thi
On Mon, Aug 29, 2005 at 02:45:33PM +0100, Vladimir Kanazir wrote:
> WTF? Is it so hard to use damn indexes? With who I need to sleep to make
> this work?
support department, maybe?
--
Alvaro Herrera ()
Este mail se entrega garantizadamente 100% libre de sarcasmo.
---(e
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 29 August 2005 21:13
> To: Dave Page; Tom Lane
> Cc: pgsql-bugs@postgresql.org
> Subject: RE: [BUGS] CVS Head: Pg_ctl bug?
>
> Though I don't see any of this code changing lately, so I
> don't see why
> it
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Though I don't see any of this code changing lately, so I don't see why
> it's failing now. Are you running it under some kind of different
> environment than you used to?
Well, are we sure that it was working for Dave before? Maybe it's a
long-stan
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 29 August 2005 21:12
> To: Dave Page
> Cc: Magnus Hagander; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] CVS Head: Pg_ctl bug?
>
> "Dave Page" writes:
> >> In some cases it writes to the eventlog instead of st
> >> In some cases it writes to the eventlog instead of stderr.
>
> > Yes, this is what's happening. Odd though, considering that I have:
> > #log_destination = 'stderr'
> > In my out-of-the-box config.
>
> pg_ctl doesn't read the config file, though. Probably we
> need to make write_stderr aw
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 29 August 2005 20:58
> To: Tom Lane; Dave Page
> Cc: pgsql-bugs@postgresql.org
> Subject: RE: [BUGS] CVS Head: Pg_ctl bug?
>
> > Is write_stderr() broken on Windows?
>
> In some cases it writes to the even
> > > Is write_stderr() broken on Windows?
> >
> > In some cases it writes to the eventlog instead of stderr.
> > Dave, can you
> > check if this is what's happening to you?
>
> Bah, no coffee for 2 weeks dulls the mind :-(
>
> Yes, this is what's happening. Odd though, considering that I have:
"Dave Page" writes:
>> In some cases it writes to the eventlog instead of stderr.
> Yes, this is what's happening. Odd though, considering that I have:
> #log_destination = 'stderr'
> In my out-of-the-box config.
pg_ctl doesn't read the config file, though. Probably we need to
make write_stder
> > I just noticed that if I don't specify a data directory
> either on the
> > command line or in $PGDATA,, pg_ctl fails silently on
> Windows (haven't
> > been able to test other platforms atm). Is this a bug or an
> oversight
> > - an error message would seem appropriate?
>
> On my machin
"Dave Page" writes:
> I just noticed that if I don't specify a data directory either on the
> command line or in $PGDATA,, pg_ctl fails silently on Windows (haven't
> been able to test other platforms atm). Is this a bug or an oversight -
> an error message would seem appropriate?
On my machine i
"Vladimir Kanazir" <[EMAIL PROTECTED]> writes:
> I can't stand it any more. Please fix damn indexes once for all, if you are
> able to.
You expect to get a polite response to this sort of thing? Especially
when you didn't show us any actual information (like EXPLAIN ANALYZE
output --- EXPLAIN alo
On Sunday 28 August 2005 01:19, Dustin Sallings wrote:
> http://www.postgresql.org/developer/beta
> links to
> http://www.postgresql.org/developer/support/submitbug
> should link to
> http://www.postgresql.org/support/submitbug
>
Fixed in cvs, will update with the
The following bug has been logged online:
Bug reference: 1855
Logged by: Vladimir Kanazir
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: linux
Description:usage of indexes
Details:
Guys,
I can't stand it any more. Please fix damn indexe
I just noticed that if I don't specify a data directory either on the
command line or in $PGDATA,, pg_ctl fails silently on Windows (haven't
been able to test other platforms atm). Is this a bug or an oversight -
an error message would seem appropriate?
/D
[EMAIL PROTECTED]:/usr/local/pgsql$ bin
On Mon, Aug 29, 2005 at 09:11:06AM -0700, Stephan Szabo wrote:
> On Mon, 29 Aug 2005, Christian Almeida wrote:
> > Should this sql work?
>
> Yes and no. ;) Whether this errors or adds the reference is controlled by
> a configuration variable, add_missing_from. For backwards compatibility
> reaso
On Mon, Aug 29, 2005 at 09:11:06 -0700,
Stephan Szabo <[EMAIL PROTECTED]> wrote:
>
> On Mon, 29 Aug 2005, Christian Almeida wrote:
>
> > Should this sql work?
>
> Yes and no. ;) Whether this errors or adds the reference is controlled by
> a configuration variable, add_missing_from. For backw
On Mon, 29 Aug 2005, Christian Almeida wrote:
> Should this sql work?
Yes and no. ;) Whether this errors or adds the reference is controlled by
a configuration variable, add_missing_from. For backwards compatibility
reasons (and for allowing outside table references in delete) the variable
cur
The following bug has been logged online:
Bug reference: 1854
Logged by: Christian Almeida
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP SP2
Description:SQL Bug
Details:
Should this sql work?
I just picked 3 tables from pg_ca
Tom Lane wrote:
"fischer" <[EMAIL PROTECTED]> writes:
c99 -O3 -mips4 -woff 1164,1171,1185,1195,1552 -I. -I../../../src/include
-I/usr/local/include -I/usr/local2/include -I/usr/nekoware/include
-U_NO_XOPEN4 -c -o analyze.o analyze.c
Signal: Segmentation fault in Global Optimizati
20 matches
Mail list logo
