Olaf Hartmann <[EMAIL PROTECTED]> writes:
> We expirience a memory leak with every connection when using an SSL
> encrypted TCP connection to connect a postgres database.
I can verify this locally. Unfortunately, my copy of valgrind doesn't
seem to be picking up the debugging symbols for OpenSSL,
Josh Berkus <[EMAIL PROTECTED]> writes:
> Summary: attempting to connect via MD5 authentication as a user
> who has no password triggers a core dump of Postmaster.
[...]
> Core dump file is available.
Can you post a stacktrace? (Building the postmaster with debugging
symbols first would be n
PostgreSQL Bugs List wrote:
The following bug has been logged online:
Bug reference: 1000
Logged by: Dave Page
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.5 Dev
Operating system: FreeBSD www.postgresql.com 4.8-STABLE FreeBSD 4.8-STABLE #5: Sat Sep 20 14:56:14 ADT 2
The following bug has been logged online:
Bug reference: 1000
Logged by: Dave Page
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.5 Dev
Operating system: FreeBSD www.postgresql.com 4.8-STABLE FreeBSD 4.8-STABLE #5: Sat
Sep 20 14:56:14 ADT 2003 [EMAIL PROTECTED]:/usr/
Olleg writes:
> > because of this kind of name conflict. There is a contributed macro that
> > automatically prefixes all macro names so they don't conflict. May be
> > worth checking out.
>
> ??? Please explain.
http://ac-archive.sourceforge.net/guidod/ax_prefix_config_h.html
---
Hi,
I have been using the C libraries with version
7.33 to retrieve data with success. Now I have
migrated to 7.4., although using the psql client all
looks fine my integer values returned through the
programmatic interface are wild, e.g. should be 101
and is 7236487.
Char and varchar are
Tom Lane wrote:
Olleg <[EMAIL PROTECTED]> writes:
It's bug, autoconf headers may not be included in "library headers".
If you think it's a bug you'd better complain to the autoconf people.
pg_config.h is generated entirely by autoconf tools.
The most libraries use autoheader, but don't generate
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the problem
I'm not really sure how to go about debugging this, but when I use PHP
to create large objects using libpq, with the php odbc module installed,
I get the following seg fault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226627936 (LWP 28034)]
0xb69f7987 in CC_send_
When using "pg_restore -S postgres -s -vcd DBNAME bkupfile" on an
existing database, I get the following error:
pg_restore: connecting to database for restore
pg_restore: dropping RULE au_d_assigned_template
pg_restore: dropping RULE au_u_assigned_template
... More rules, triggers, constraints, i
POSTGRESQL BUG REPORT TEMPLATE
Your name : Olaf Hartmann
Your email address : [EMAIL PROTECTED]
System
Your name : Claus Colloseus
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture : AMD Athlon XP 2000+
Operating System : Windows 2000 V. 5.00.2195
PostgreSQL version: PostgreSQL-7.4
Compiler used
Severity: Core dump
Frequency: Unusual
PostgreSQL Version: 7.4.0 release
Platform:
Solaris 8
gmake 3.80
gcc 3.23
440mhz UltraSparc III
Netra T1/105
Reproducability: 100% on this machine and an identical one.
Not yet tested on other machines runn
Peter Eisentraut wrote:
Tom Lane writes:
Olleg <[EMAIL PROTECTED]> writes:
It's bug, autoconf headers may not be included in "library headers".
If you think it's a bug you'd better complain to the autoconf people.
pg_config.h is generated entirely by autoconf tools.
Admittedly, you're not suppos
Tom Lane wrote:
> Olleg <[EMAIL PROTECTED]> writes:
> > olleg=# \set AUTOCOMMIT OFF
>
> It has to be
>
> \set AUTOCOMMIT off
>
> Not sure if we should be more flexible about this or not. The code says
>
> /*
>* for backwards compatibility, anything except "off" is taken as
15 matches
Mail list logo
