Hello,
this is very severe condition. I hope, that PostgreSQL team can correct it.
I can provide any additional information you need, including whole database
or a shell account for testing on my host.
It appears to work on 7.1.2 and 7.1.3 on FreeBSD 4.3-STABLE. It is fully
repeatable bug.
Thi
Michał Pasternak [Thu, Sep 06, 2001 at 12:25:24PM +0200]:
> But this doesn't (and I need it to work):
>
> TYTUL_OR ILIKE 'Ocena%' OR TITLE LIKE 'Ocena%';
> TYTUL_OR LIKE 'Ocena%' or TITLE LIKE 'Ocena%';
Uh, I forgot: server starts to output something, which looks like a one row,
one-
Hi Bruce,
On Wed, 5 Sep 2001, Bruce Momjian wrote:
> I have a patch here that handles all the TCL/UTF issues.
> Would you let me know if it is OK?
I think, it isn't really a clean fix. It only works, if your
database's encoding and Tcl's system encoding are identical. If the
database uses a dif
> Sample Code
> CREATE FUNCTION check_key(varchar,varchar) RETURNS OPAQUE AS '
> BEGIN
> IF COUNT(*) FROM $2 WHERE $2.$1=NEW.$1 THEN
>RAISE EXCEPTION ''integrity violation : duplicated key'';
> END IF;
> RETURN NEW;
> END;
> ' LANGUAGE 'plpgsql';
>
> CREATE TRIGGER trigger_
arnauld michelizza ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
trigger can not find a function
Long Description
ERROR: CreateTrigger: function check_key() does not exist
Sample Code
CREATE FUNCTION check_key(varchar,varc
Hi,
I have a serious problem with hanging backends.
This is wat I get from ps ->
postgres 23507 22794 0 13:33 ?00:00:09
/usr/local/pgsql/bin/postgres 1.1.3.123 postgres bts01 SELECT waiting
This blocks all the other clients. (ODBC call failed)
The situation
- PostgreSQL 6.4.2 on i
I need in some select-statements case-insensetiv ordering of results,
i want to use upper()-function in order by part of statement but it
doesn't work with field-aliases.
Can I do this in another way?
I'm using PostgreSql 7.1.2 on SuSe-Linux
Example:
this works:
select p1.prs_vorname as v
[EMAIL PROTECTED] writes:
> - PostgreSQL 6.4.2 on i686-pc-linux-gnu, compiled by gcc 2.7.2.
> In which direction do I have to search?
Try a more recent release, for starters. PG 7.1.3 is current.
(You might want to find a less ancient gcc version, too...)
regards, tom
Steve Pothier <[EMAIL PROTECTED]> writes:
> PostgreSQL version (example: PostgreSQL-6.5.1): PosegreSQL 7.1
> hbase=# SELECT * FROM subject WHERE subject_id LIKE '0009%' UNION (SELECT * FROM
>subject WHERE subject_id LIKE '0008%' LIMIT 5);
> ERROR: parser: parse error at or near "limit"
Are
John Summerfield <[EMAIL PROTECTED]> writes:
> I have postmaster configured to use syslog. Despite this, these messages appear on
>the terminal from which I start it:
> 2001-09-03 23:44:37 [26371] DEBUG: recycled transaction log file 0044
Very strange. That shouldn't be happening
I'm building a 3-dimensional array using 5 tables; 3 of them define the
headings for the 3 dimensions, a fourth states the valid combinations
of labels, and the 5th table matches combinations to values.
I want to populate the first 4 tables all at the same time; by providing
the grid which define
There is a change in html output construction in the 7.1 series
that I have had difficulty handling.
In a prior version (7.0.x, I think) invoking psql with -H command line
switch and a select statement of the following form:
select '' || 'link text ' from table
where
produced a html t
=?iso-8859-2?B?o3VrYXN6IFNrb3dyb/Fza2k=?= <[EMAIL PROTECTED]> writes:
> I created a view named some_view. Postgresql behaves quite strange
> because it creates some_view file which has almost 600 MB.
Uh ... what PG version is this? In recent releases views don't even
*have* any associated fi
I checked into this and it is pretty hard to fix. You can edit
bin/psql/tab-completion.c if you wish.
> Don Pellegrino ([EMAIL PROTECTED]) reports a bug with a severity of
>4
> The lower the number the more severe it is.
>
> Short Description
> psql \d+ does not support tab completion as \d
[EMAIL PROTECTED] writes:
> My pattern of use for ``CREATE RULE... NOTIFY...'' was, up to now, to get
> a notice when anything changed on a table and then go look what happened;
> a `poor man's statement level trigger' if you wish. Thus, the old behavior
> didn't bother me that much. I don't know
On Thu, Sep 06, 2001 at 03:16:26PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > versuch=# CREATE RULE ru_u_chkntfy AS ON UPDATE TO chkntfy DO NOTIFY CHKNTFY;
> > CREATE
> > versuch=# update chkntfy set nummer=10 where nummer = 1;
> > ERROR: Conditional NOTIFY is not implemented
>
>
With the following configure script:
CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-syslog \
--with-CXX --with-perl --enable-multibyte --enable-cassert \
--with-includes=/usr/local/include --with-libs=/usr/local/lib \
--enable-debug \
--with-tcl --wit
Tom Lane writes:
> > What we probably want is some configure switch that switches between the
> > current behaviour and the behaviour you want.
>
> I'd suggest --prefix-like options to determine installation locations
> for the perl and python modules,
Basically, I was envisioning some option li
18 matches
Mail list logo