Skip site navigation (1) Skip section navigation (2)

Re: upper() problem in 7.0.2

From: "Christopher L(dot) Cousins" <chris(at)impulse(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Christopher L(dot) Cousins" <chris(at)impulse(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: upper() problem in 7.0.2
Date: 2000-07-06 19:23:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, Jul 06, 2000 at 03:18:59AM -0400, Tom Lane wrote:
> "Christopher L. Cousins" <chris(at)impulse(dot)net> writes:
> > What I can do is create a fake dataset, find some values that cause the problem, then give
> > that to you.  Would that be acceptable?
> Sure, if you can do that.  I just want to reproduce the crash here.

Ok, the fake dataset, sample output, and the tools used are available here:

bad.out                       psql output of the known bad strings.
data.sql                      fake dataset generated from
dump.out                      pg_dump of the the database.
known_bad_strings             a list of strings known to cause the crash.
pgsql-bugs.tar.gz             all of the files in this directory.                      wrapper for
schema.sql                    schema for the database.
select.out                    query for each username in the database using psql -e                     used to create select.out   used to create bad.out          used to create data.sql, fake dataset.
username.out                  list of all "usernames" in the dataset.



Impulse Internet Services    /    \
____________________________/      \_____ <chris(at)impulse(dot)net>

In response to

pgsql-bugs by date

Next:From: Christopher L. CousinsDate: 2000-07-06 20:45:13
Subject: Re: upper() problem in 7.0.2
Previous:From: planx plnetxDate: 2000-07-06 16:19:17
Subject: Humongous BUG in libpq???

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group