On Tue, 14 Feb 2006, Jens-Wolfhard Schicke wrote:
> --On Montag, Februar 13, 2006 21:25:30 -0500 Stephen Frost
> <[EMAIL PROTECTED]> wrote:
>
> > * Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> >> > Seems kind of unlikely... What exact (.deb) versions of libpq and
> >> > Postgres are you using?
On Tue, 14 Feb 2006, Andrew Klosterman wrote:
> > We may be spending too much time on this one point --- as long as
> > Kerberos isn't *writing* into the zero-length alloc, there is nothing
> > illegal immoral or fattening about malloc(0). Can you get ElectricFence
> > to not abort right here but
The following bug has been logged online:
Bug reference: 2264
Logged by: Alex Kostyshin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.x
Operating system: Windows XP/SP2, Windows XP x64
Description:bad work with cyrillic encoding
Details:
1. Wrong sorting
On Tue, 14 Feb 2006, Andrew Klosterman wrote:
> On Mon, 13 Feb 2006, Stephen Frost wrote:
>
> > Hmm, alright, well, this is at least not the fault of the patch of mine
> > which was included in Debian's 8.1.2-2 Postgres release. :) You might
> > try compiling some debs with debugging enabled. Th
The following bug has been logged online:
Bug reference: 2263
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Linux x86
Description:corrupted pgstat.stat file
Details:
Hello!
I upgraded from 8.1.2 to 8.1.3 without dumping (w
On Tue, 14 Feb 2006, Stephen Frost wrote:
> It's kind of a chicken-and-egg here because the backend decides what
> authentication mechanism to ask for based off the username (at least in
> part) through pg_hba.conf, so you can't find out the authentication
> method until you know the username so a
> We may be spending too much time on this one point --- as long as
> Kerberos isn't *writing* into the zero-length alloc, there is nothing
> illegal immoral or fattening about malloc(0). Can you get ElectricFence
> to not abort right here but continue on to the real problem?
>
>
The following bug has been logged online:
Bug reference: 2259
Logged by: Michal Dvoracek
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Debian testing
Description:never ending select from selects
Details:
Hello,
this query runs very lo
The following bug has been logged online:
Bug reference: 2262
Logged by: Richard Baverstock
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP Pro
Description:WHERE-clause comparisons wrong
Details:
History: Imported data from an 8
The following bug has been logged online:
Bug reference: 2260
Logged by: Daniel Blaisdell
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Gentoo Linux K:2.6.9
Description:PGCrypto Memory Problem
Details:
Prereq:
PGCrypto
Table Setup:
e
> > Tracking down exactly what's tickling the problem in this case could be
> > tricky...
>
> Yeah :-(. If you aren't able to narrow it further by yourself, please
> try to put together a self-contained test case.
>
> regards, tom lane
Well, my attempt last night at putting
On Mon, 13 Feb 2006, Stephen Frost wrote:
> Hmm, alright, well, this is at least not the fault of the patch of mine
> which was included in Debian's 8.1.2-2 Postgres release. :) You might
> try compiling some debs with debugging enabled. This is (reasonably)
> straight-forward:
>
> (as root:)
>
The following bug has been logged online:
Bug reference: 2261
Logged by: Evgeny Gridasov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Debian Linux
Description:ILIKE seems to be buggy on koi8 input
Details:
my terminal is RU_ru.KOI8-R,
Andrew Klosterman <[EMAIL PROTECTED]> writes:
> With the debug binaries, I was able to step through the program and get to
> what appears to be the function where it bails: line 1166 of
> postgresql-8.1.0/src/interfaces/libpq/fe-secure.c where SSL_free() is
> called.
BTW, is the address that glib
"" <[EMAIL PROTECTED]> writes:
> I upgraded from 8.1.2 to 8.1.3 without dumping (was not required). After
> starting I got this error in the logs:
> LOG: corrupted pgstat.stat file
> What should I do?
Ignore it. We changed the format of the pgstat file between 8.1.2 and
8.1.3.
2006-01-18 15:3
"Evgeny Gridasov" <[EMAIL PROTECTED]> writes:
> my terminal is RU_ru.KOI8-R,
> template1's encoding is UTF8.
> ILIKE seems to be buggy when comparing russian strings,
> while UPPER/LOWER works OK.
I'll bet that the database's locale setting is expecting some encoding
other than UTF8 :-(. You need
On Tue, Feb 14, 2006 at 05:28:25PM +, Daniel Blaisdell wrote:
> Problem Query:
> select * from table where md5password = crypt('password',salt)
>
> The first time this query is run, I see the postgres process bump up to 8MB
> of ram from where it initializes.
>
> On subsequent issues of the s
"Daniel Blaisdell" <[EMAIL PROTECTED]> writes:
> Table Setup:
> employeeid integer
> salt text
> md5password text
> Problem Query:
> select * from table where md5password = crypt('password',salt)
I tried this with dummy data and couldn't see any memory leak, using
Fedora Core 4 and CVS-tip postgr
"Michal Dvoracek" <[EMAIL PROTECTED]> writes:
> this query runs very long time - after hour i cancelled it.
The EXPLAIN output is just about unreadable as you've posted it ---
could you fix that and repost? Also please provide EXPLAIN ANALYZE
output for all the cases that do finish in a reasonabl
Michael Fuhr <[EMAIL PROTECTED]> writes:
> I can reproduce this in 8.1.3 on FreeBSD 6.0 and Solaris 9. Here's
> a standalone test case:
> SELECT crypt(x::text, '$1$salt') FROM generate_series(1, 500) AS g(x);
Interesting, because I see no leak with this example on Fedora 4 or
HPUX. Platform dep
On Wed, Feb 15, 2006 at 01:43:18PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I can reproduce this in 8.1.3 on FreeBSD 6.0 and Solaris 9. Here's
> > a standalone test case:
>
> > SELECT crypt(x::text, '$1$salt') FROM generate_series(1, 500) AS g(x);
>
> Interesting, be
Lee Thompson <[EMAIL PROTECTED]> writes:
> Better version of patch. Only kicks in when asked for
> with --enable-rpath_sl
You still haven't explained why such a change is needed. We're unlikely
to accept a patch without explanation, especially given that the
existing build system works fine on a
Better version of patch. Only kicks in when asked for
with --enable-rpath_sl
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> "Lee Thompson" <[EMAIL PROTECTED]> writes:
> > +if test "$enable_rpath" = yes ; then
> > + LIBDIRS="$LIBDIRS -Wl,-R$dir"
> > +fi
>
> What is this supposed to accom
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Wed, Feb 15, 2006 at 01:43:18PM -0500, Tom Lane wrote:
>> Interesting, because I see no leak with this example on Fedora 4 or
>> HPUX. Platform dependency is sounding more and more likely.
> Did you test OpenSSL builds?
Nope, I did not, and that's a
On Wed, Feb 15, 2006 at 02:28:33PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Did you test OpenSSL builds?
>
> Nope, I did not, and that's a good point. Will try again with openssl.
My non-OpenSSL build shows no memory leak, so the leak and OpenSSL
seem to be correlate
Michael Fuhr <[EMAIL PROTECTED]> writes:
> My non-OpenSSL build shows no memory leak, so the leak and OpenSSL
> seem to be correlated. I'd be more inclined to suspect a bug in
> pgcrypto's OpenSSL-specific code than in OpenSSL itself. Will keep
> digging.
The problem appears to be here:
static
26 matches
Mail list logo
