-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Tom> Raj Mathur <[EMAIL PROTECTED]> writes:
>> I'm consistently getting into a situation where the database
>> client just goes to sleep in a query after some number of
>> queries in
Title: -- CONFIDENTIALITY NOTICE --
-- CONFIDENTIALITY NOTICE --
This
message is intended for the sole use of the individual and entity to whom it is
addressed, and may contain information that is privileged, confidential and
exempt from disclosure under applicable law. If you are not the
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Like "--with-perl"? The reason that got in there was not to deal with
>> weird compiler flags, it was to deal with the standard Perl installation
>> on RHL 8.0.
> But for that purpose it was sufficient to leave it in linux.h.
But
Tom Lane writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I don't agree with cluttering the compile line with -D_GNU_SOURCE just for
> > the case when someone adds additional unsupported compiler flags.
>
> Like "--with-perl"? The reason that got in there was not to deal with
> weird co
Hello fellas,
I made a VB application with PeerDirect-PostgreSQL 7.2
Under Win2K.
The application and the DB are working fine, however I would
like to do an automatic BackUp process activated from my VB
application.
Any Ideas,
Thank you in advanced for any sugestion.
MAGO
__
On Fri, 26 Sep 2003, Peter Eisentraut wrote:
> Stephan Szabo writes:
>
> > It's not a problem for me unless I'm compiling with CFLAGS="-std=c89".
>
> Don't do that then. :-)
Well, the discussion started with Tom trying to find an option that
disallowed // comments for gcc. :)
> I don't agree wit
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Fundamentally however, having configure run with a fundamentally different
> compilation environment from an actual build (which _GNU_SOURCE basically
> does) is dangerous.
Yes, having put _GNU_SOURCE into the port header rather than the port
template fi
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I don't agree with cluttering the compile line with -D_GNU_SOURCE just for
> the case when someone adds additional unsupported compiler flags.
Like "--with-perl"? The reason that got in there was not to deal with
weird compiler flags, it was to deal
Stephan Szabo writes:
> It's not a problem for me unless I'm compiling with CFLAGS="-std=c89".
Don't do that then. :-)
I don't agree with cluttering the compile line with -D_GNU_SOURCE just for
the case when someone adds additional unsupported compiler flags. We
might as well add -fhosted just
This has been saved for the 7.5 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Achilleus Mantzios wrote:
>
> Hi,
>
> any news on applying the patches to dbmirror??
>
> Thanx.
>
>
> On Sun, 10 Au
On Fri, 26 Sep 2003, Peter Eisentraut wrote:
> Stephan Szabo writes:
>
> > Configure doesn't find struct addrinfo (because it's in a __USE_POSIX
> > block) so it looks like we use our own version, but, when we're actually
> > then compiling getaddrinfo.c, there's a redefinition error because this
Stephan Szabo writes:
> Configure doesn't find struct addrinfo (because it's in a __USE_POSIX
> block) so it looks like we use our own version, but, when we're actually
> then compiling getaddrinfo.c, there's a redefinition error because this
> time struct addrinfo is found (because _GNU_SOURCE fo
Tom Lane wrote:
> and the problem is that HAS_CRYPT_R has gotten defined but "struct
> crypt_data" has not. It's been awhile since I looked at this, but I
> think that Perl configures HAS_CRYPT_R on the basis of a link-only test
> for crypt_r(), which will succeed regardless of -D symbols. And (i
Bruce Momjian <[EMAIL PROTECTED]> writes:
> That _GNU_SOURCE has always bothered me. What does it control, exactly?
> It seems to control a lot.
Well, without it I get (on RHL 8.0)
gcc -O2 -g -fpic -I. -I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE
-I../../../src/include -c -o plperl.o p
Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > It looks like commenting it out of linux.h and adding it to template/linux
> > works for the main build, it compiles and links fine both with and without
> > --std=c89 and the latter also passes regression. I didn't try to build
> > p
Stephan Szabo <[EMAIL PROTECTED]> writes:
> It looks like commenting it out of linux.h and adding it to template/linux
> works for the main build, it compiles and links fine both with and without
> --std=c89 and the latter also passes regression. I didn't try to build
> plperl however.
Okay, I ve
Hi List;
Where can I find a plan-readinf tutorial ?
Atenciosamente,
Rhaoni Chiu Pereira
Sistêmica Computadores
Visite-nos na Web: http://sistemica.info
Fone/Fax : +55 51 3328 1122
---(end of broadcast)---
TIP 6: Have you searched our li
On Fri, 26 Sep 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > However, the immediate problem I have seems to come from the fact that
> > on Linux at least we're basically lying to configure about what's in the
> > system headers when we go to compile. port/linux.h on my sys
Stephan Szabo <[EMAIL PROTECTED]> writes:
> However, the immediate problem I have seems to come from the fact that
> on Linux at least we're basically lying to configure about what's in the
> system headers when we go to compile. port/linux.h on my system defined
> _GNU_SOURCE which forces most/all
On Fri, 26 Sep 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> >> I've been through them. None of 'em turn off // comments. Or #-sign
>
> > On at least some versions of gcc it looks like --std=c89 turns them off
>
> Hmm, I haven't tried that in particular. I wonder what els
On Thu, 25 Sep 2003, Tom Lane wrote:
> "Donald Fraser" <[EMAIL PROTECTED]> writes:
> >> Nice work, just two comments (1) the C++ comment style (//) is not
> >> portable for C programs and should be changed and (2) the standard way
>
> > Fair comment but since it has to be compiled against a valid
On Fri, Sep 26, 2003 at 08:35:54 -0400,
Jodi Kanter <[EMAIL PROTECTED]> wrote:
> Is there any argument to support using table constraints over column
> constraints in a situation where there are no PKs or FK references that
> are composed of more than one column?
Functionally they should be th
At 06:24 PM 9/25/2003 , Tom Lane wrote:
>Larry Rosenman <[EMAIL PROTECTED]> writes:
> >> We have several beta testers who keep us honest on exactly this point;
> >> they use compilers that do not take //. Personally I wish gcc could
> >> be configured not to have these little non-ANSI-isms ...
I
Title:
Is there any argument to support using table constraints over column constraints
in a situation where there are no PKs or FK references that are composed
of more than one column?
Is the automatic PK index generated on for table constraints or for either?
J
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Tom> Raj Mathur <[EMAIL PROTECTED]> writes:
>> I'm consistently getting into a situation where the database
>> client just goes to sleep in a query after some number of
>> queries in quick succession. Using PostgreSQL 7.2.3 on Red
25 matches
Mail list logo
