On Thu, 26 Oct 2000, Oliver Elphick wrote:
> The following sequence, which works in 7.0.2, now fails in current
> sources:
> [example snipped]
>
> I think this means that the FOREIGN KEY installer thinks that table
> "individual" does not have columns "id" and "address", which are
> inherited f
"Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> Were you aware that this is legal:
> (select avg(a),b from dummy group by b) order by b;
> but this is not:
> (select avg(a),b from dummy) group by b order by b;
The reason for that is that SQL doesn't think that "order by" should
be allowed in s
After reviewing a number of past threads about the INET/CIDR mess,
I have concluded that we should adopt the following behavior:
1. A data value like '10.1.2.3/16' is a legal INET value (it implies
the host 10.1.2.3 in the network 10.1/16) but not a legal CIDR value.
Hence, cidr_in should reject
[EMAIL PROTECTED] wrote:
I've been looking into this. I thought it would be easy, but it
doesn't want an easy fix, because it's worse than it at first
appeared.
Were you aware that this is legal:
(select avg(a),b from dummy group by b) order by b;
but this is not:
(select avg(a),b from dumm
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Saw Tom's commits, now it breaks here:
> cc -c -I/usr/local/include -I../../../src/include -DFRONTEND -I.
>-DSYSCONFDIR='"/home/ler/pg-test/etc/postgresql"' -O -K inline -K PIC -o fe-connect.o
>fe-connect.c
> UX:acomp: ERROR: "../../../src/include/mb/
The following sequence, which works in 7.0.2, now fails in current
sources:
CREATE TABLE person
(
ptypeSMALLINT,
id CHAR(10)PRIMARY KEY,
name TEXTNOT NULL,
address INTEGER REFERENCES address (id)
Added to TODO:
* Prevent initdb from running wrong version of postmaster/postgres
> While answering the n'th why-is-initdb-failing question that looked like
> a version mismatch problem, it occurred to me to wonder why we don't
> make initdb verify that the executable and library files it's usin
Tom Lane wrote:
>Larry Rosenman <[EMAIL PROTECTED]> writes:
>> Tried --enable-multibyte for grins. Bad Move.
>
>> Undefined first referenced
>> symbol in file
>> reset_client_encoding tcop/SUBSYS.o
>
>Ooops, I guess I broke
Hello!
Its, may be ,little "gluk" in doc, - sources and docs and examples
for Create Rule not correlated.
Conctrento :)) ->
÷ ÄÏËÅ ->
CREATE RULE example_1 AS
ON UPDATE emp.salary WHERE old.name = "Joe"
/* ^^^ */
DO
UPDATE emp
SET salary = ne
http://www.l-t.ee/marko/pgsql/pgcrypto-0.2c.diff (context diff)
http://www.l-t.ee/marko/pgsql/pgcrypto-0.2u.diff (unidiff)
http://www.l-t.ee/marko/pgsql/pgcrypto-0.2.tar.gz
diffs are for currect CVS - contrib/pgcrypto, tarball is
standalone variant with autoconf and 7.0.x compat hacks.
Whats
Sounds like an easy one for a newbie to pick up. Let me look at it,
but I think I'd like dibs on it.
LER
* Tom Lane <[EMAIL PROTECTED]> [001026 13:29]:
> While answering the n'th why-is-initdb-failing question that looked like
> a version mismatch problem, it occurred to me to wonder why we do
Saw Tom's commits, now it breaks here:
gmake[3]: Leaving directory `/home/ler/pg-dev/pgsql/src/backend/utils'
cc -O -K inline -o postgres access/SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o
parser/SUBSYS.o commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o
main/SUBSYS.o nodes/SUBSY
Pete Forman writes:
> There is a separate problem running the configure script on AIX. It
> hangs while testing for flex. The two processes that I killed to
> allow configure to continue were
>
> /usr/ccs/bin/lex --version
> /usr/bin/lex --version
>
> The problem is that lex is waitin
While answering the n'th why-is-initdb-failing question that looked like
a version mismatch problem, it occurred to me to wonder why we don't
make initdb verify that the executable and library files it's using
are all from the same release it is. I think this would eliminate an
installation mista
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Tried --enable-multibyte for grins. Bad Move.
> Undefined first referenced
> symbolin file
> reset_client_encoding tcop/SUBSYS.o
Ooops, I guess I broke that yesterday :-(. Will fix.
Larry Rosenman writes:
> OpenSSL dies:
Yeah, I saw that too yesterday. Not sure if I want to blame your crypt.h
header or what. Don't know what to do yet, but it ought to get fixed.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
It seems like postgres is thinking that the query is incorrectly
formatted. Do you know what query is being run when this happens?
You may wish to start the postmaster with -d2 which should print
out the queries that postgres is seeing.
Stephan Szabo
[EMAIL PROTECTED]
On Wed, 25 Oct 2000, andr
Alex Pilosov <[EMAIL PROTECTED]> writes:
> I need some of features (union in views, in particular) which are only
> available in 7.1-current. How insane would be to try it on production
> server? Are there known bugs that could cause loss of data or loss of
> updates? Or just newer features aren't
Tried --enable-multibyte for grins. Bad Move.
Top part of config.status:
#! /bin/sh
# Generated automatically by configure.
# Run this file to recreate the current configuration.
# This directory was configured as follows,
# on host lerami.lerctr.org:
#
# ./configure --prefix=/home/ler/pg-te
Tom Lane wrote:
> In situations like SQL function calls, it may be necessary to suspend
> a table scan while we go off and do other commands, then come back and
> resume the table scan. So there can be multiple scans with different
> command IDs in progress within a transaction.
Ohh yes .. you a
At 11:22 25/10/00 -0400, Jeff Tucker wrote:
SELECT setval('products_seq_id',100); but for some reason it is no longer working. It would previously return 100 and now it returns nothing and the counter is not increased to 100. Any suggestions on where to look?
Which version are you us
Michael Meskes wrote:
> What do other DBs do with their output variables if there is an embedded SQL
> query resulting in a NULL return value? What I mean is:
>
> exec sql select text into :txt:ind from ...
>
> If text is NULL, ind will be set, but does txt change?
>
> I was just told Informix bl
Philip Warner wrote:
> At 09:36 25/10/00 +0200, Zeugswetter Andreas SB wrote:
> >
> >> I have not followed the entire thread, but if you are in a serializable OR
> >> repeatable-read transaction,
> >
> >Serializable and repeatable read are the same thing, different wording.
>
> Not last time I l
I need some of features (union in views, in particular) which are only
available in 7.1-current. How insane would be to try it on production
server? Are there known bugs that could cause loss of data or loss of
updates? Or just newer features aren't polished yet?
Also, where is cvs repository? Is
24 matches
Mail list logo
