"David Kensiski" writes:
> The psql binary (64-bit from binary install) dumps core when I attempt to
> edit the input line after a few characters are entered:
This most likely indicates a problem with the libreadline or libedit
library you're using.
regards, tom lane
--
The following bug has been logged online:
Bug reference: 5631
Logged by: David Kensiski
Email address: da...@schoolloop.com
PostgreSQL version: 8.4
Operating system: Solaris 10
Description:psql dumps core during command editing
Details:
The psql binary (64-bit from
"tbz" writes:
> CREATE TABLE pg_user (
> login_name VARCHAR(50) NOT NULL
> );
> CREATE UNIQUE INDEX ak1_login_name ON pg_user(login_name);
> [fails]
This is expected, given the default search_path settings in which
pg_catalog is implicitly at the front of the path. When you create
pg_user, it's
The following bug has been logged online:
Bug reference: 5630
Logged by: tbz
Email address: t...@vollbio.de
PostgreSQL version: 8.3.11
Operating system: Debian Sqeeze
Description:CREATE INDEX does not use schema search path
Details:
1. Create a new schema like a log
Alexsander Rosa writes:
> Let me get this straight: in version 8.3 the ALTER SEQUENCE command has an
> *undocumented* [1] clause START that is actually an alias for RESTART (i.e.
> both reset the sequence value to the value passed by the mandatory
> argument).
Yeah. I just looked at the old code
-- Forwarded message --
From: Alexsander Rosa
Date: 2010/8/27
Subject: Re: [BUGS] BUG #5629: ALTER SEQUENCE foo START execute a RESTART
To: Tom Lane
Let me get this straight: in version 8.3 the ALTER SEQUENCE command has an
*undocumented* [1] clause START that is actually an ali
