Lee Kindness ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
ECPG does not correctly identify pointer type
Long Description
The embedded SQL preprocessor, ecpg, does not correctly identify pointer types.
Example #1 below resul
Hi, I have a problem I am using postgresql database and I want to enforce
>triggers between my related tables ( tables with relationship), one
table
>has a foreign key and the other the a primary key, I would like to use
>triggers to update, delete, and insert in this tables but the tabl
Doing a default ./configure (no additional options) on a freshly installed OpenBSD 2.9
results in a 'psql' binary that isn't linked to termcap. The error looks like this:
$ ./psql
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help
Hellow.
Unfortunaly for me postgresql 7.1.2 builds by default with WAL (and there were'n
configure options to turn it of). So one of files in $database/xlog was corrupted.
Postgres is not starting cose of corrupted WAL files:
===
DEBUG: database system was shut down at 2001-08-13 18:38:03 MSD
D
Hi,
As far as I can tell from the documentaion, it is impossible to tell the
postmaster daemon to bind to just a single IP address - only to a
specific port on all IP addresses. This makes hardening the box
postgresql is running on impossible.
Is there a workaround to this? (other than trying to
Hello pgsql-bugs,
my name is Taras (from Russia). sorry for my bad English.
i have set the password access to connecting to the database.
hash passwords stored in the '/usr/local/pgsql/data/pg_shadow' file.
for example, username is 'lanta' and password is 'asdfghjk'
When i'm connecting
Hi,
I have found a bug in PostgreSQL doing "except all". Some records are
removed from the result, even though they should stay. Except all removed
records which were _not_ in the table that were excepted from the original
table.
I have put the data and small python code here:
http://www.webit.
Hi,
I have found a bug in PostgreSQL doing "except all".
It removes some records which it shouldnt when I run except on large data
sets. If I run the same except only on the records in question (using
where...), it shows up in the result ok.
I have put the data and small python code here:
http:
root <[EMAIL PROTECTED]> writes:
> Unfortunaly for me postgresql 7.1.2 builds by default with WAL (and
> there were'n configure options to turn it of). So one of files in
> $database/xlog was corrupted.
Do you know what happened to it? Is there a bug we need to fix here?
> So how to save my bas
[EMAIL PROTECTED] writes:
> Except all eliminates what it shouldnt
Hmm, nasty. It looks like all nested cases of INTERSECT/EXCEPT are
broken.
Attached is a patch I've applied to CVS sources (7.2-to-be). I don't
have enough confidence in it to back-patch it into 7.1.* right now,
but if you want
"Tom Stowell" <[EMAIL PROTECTED]> writes:
> "_tgetent" is a termcap symbol, and simply appending
> -ltermcap
> ...to the final gcc command during the 'psql' make fixes the problem.
> This should probably work w/o human intervention, however. :-)
Indeed. The configure script should have deduced
halturin <[EMAIL PROTECTED]> writes:
> Password: <-- entering password 'asdfghjkpmqwoeim10234'
> ^
> i have added to the password
> any char's and ...
> connec
Graham Leggett <[EMAIL PROTECTED]> writes:
> As far as I can tell from the documentaion, it is impossible to tell the
> postmaster daemon to bind to just a single IP address
Sure you can, assuming you're running a current release. See
VIRTUAL_HOST config parameter or equivalent -h commandline sw
> Hi,
>
> As far as I can tell from the documentaion, it is impossible to tell the
> postmaster daemon to bind to just a single IP address - only to a
> specific port on all IP addresses. This makes hardening the box
> postgresql is running on impossible.
>
> Is there a workaround to this? (othe
Tom Stowell writes:
> "_tgetent" is a termcap symbol, and simply appending
>
> -ltermcap
>
> ...to the final gcc command during the 'psql' make fixes the problem. This should
>probably work w/o human intervention, however. :-)
We have disqualified this as a linker bug pending OS developer fee
Bjorn Peterson ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC driver converts search string patterns to lowercase
Long Description
The metadata class of the Postgresql 7.1 JDBC driver converts search string patterns
to a
16 matches
Mail list logo
