Kris Jurka <[EMAIL PROTECTED]> writes:
> Creating a domain on bit(N) doesn't seem to work as expected when casting
> to the domain type.
> CREATE DOMAIN bit4 AS bit(4);
> SELECT 7::bit(4), 7::bit4;
> bit | bit4
> --+--
> 0111 | 1000
> (1 row)
What's going on here is that "7::bit4" i
Creating a domain on bit(N) doesn't seem to work as expected when casting
to the domain type.
CREATE DOMAIN bit4 AS bit(4);
SELECT 7::bit(4), 7::bit4;
bit | bit4
--+--
0111 | 1000
(1 row)
Reported in #postgresql by msw_alt.
Kris Jurka
---(end of broadcast
David Dick <[EMAIL PROTECTED]> writes:
> /home/dave/postgresql-8.0.0beta4/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/psql:
>
> relocation error:
> /home/dave/postgresql-8.0.0beta4/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/psql:
>
> undefined symbol: PQserverVersi
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> CREATE DATABASE
> pg_regress: could not set database default locales
This is most likely not actually locale-related at all; it's probably
got something to do with a failure to start psql. Please remove the
"2>/dev/null" in the pg_regress scrip
The following bug has been logged online:
Bug reference: 1306
Logged by: David Dick
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Debian (Woody) with a Linux 2.6.7 kernel
Description:locale related issue.
Details:
in response t
=?iso-8859-2?B?U1rbQ1MgR+Fib3I=?= <[EMAIL PROTECTED]> writes:
> BUT if I kill the first transaction (with standard (15 Terminate) signal),
> the second one stucks in "waiting".
SIGTERM on individual backends is not recommended or supported.
FWIW, though, I could not duplicate this bug report. Ar
Ð ÐÑÐ, 05.11.2004, Ð 16:46, Tom Lane ÐÐÑÐÑ:
> Markus Bertheau <[EMAIL PROTECTED]> writes:
> > Guess what happend here:
> > [EMAIL PROTECTED] pg80]$ bin/pg_ctl -D data -l log start
> > postmaster starting
> > [EMAIL PROTECTED] pg80]$
>
> > No, postmaster was not starting - it was configured to lis
Markus Bertheau <[EMAIL PROTECTED]> writes:
> Guess what happend here:
> [EMAIL PROTECTED] pg80]$ bin/pg_ctl -D data -l log start
> postmaster starting
> [EMAIL PROTECTED] pg80]$
> No, postmaster was not starting - it was configured to listen on the
> default port - and there was already another
Thank's for all
I upgrade my pg8 to beta 4 and I now it's all ok .
I didn't realize that I had checked this option on install of beta 3.
Sorry :(
Magnus Hagander wrote:
No bug; these objects exist in the template1 database -
someone created
the
Dear Gurus,
Version: PostgreSQL 7.4.3 on Linux.
I have two transactions trying to insert the same value in a unique index
(pkey).
Tested and if I simpy try two plain sql backends, everything's ok. However,
mine is a silly scenario.
Obviously, the first one locks something (I assume the tuple) si
Guess what happend here:
[EMAIL PROTECTED] pg80]$ bin/pg_ctl -D data -l log start
postmaster starting
[EMAIL PROTECTED] pg80]$
No, postmaster was not starting - it was configured to listen on the
default port - and there was already another postmaster running on 5432.
This information was of cou
11 matches
Mail list logo
