Thanks everyone for the explanations. I posted a feature request for improved
enum manipulation in psql-general.
Dmitry Epstein | Developer
Allied Testing
www.alliedtesting.com
We Deliver Quality.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscr
> -Original Message-
> From: Merlin Moncure [mailto:mmonc...@gmail.com]
> Sent: Tuesday, September 27, 2011 10:31 PM
> > 1. We can use ALTER TYPE to add enum values, but there is no matching
> command to remove values, which makes this an incomplete solution.
>
> you can manually delete fr
Hello,
I've encountered some problems with the updated ENUM in PosgreSQL 9.1:
1. We can use ALTER TYPE to add enum values, but there is no matching command
to remove values, which makes this an incomplete solution.
2. "ALTER TYPE ... ADD cannot be executed from a function or multi-command
stri
Update: It has been suggested to wrap perform around a select like this:
do
$$begin
perform(
with A as (select 1 as foo)
select foo from A
);
end$$;
This won't work if select returns more than one statement:
do
$$begin
perform(
with A as (select generate_series(1,3) as foo)
select foo from A
);
PostgreSQL 9.0.1
It seems that PostgreSQL doesn't understand the WITH construct when used in a
PERFORM query inside PL/pgSQL functions and code blocks:
Example:
do
$$begin
with A as (select 1 as foo)
perform foo from A;
end$$;
syntax error at or near "perform"
do
$$begin
with A as (select
Hello,
I noticed that when pg_dump saves SQL code for a table with inheritance, it
does not save any information about inherited columns. This is fine when
inherited columns do not undergo any modification, but when they do, that
information is lost.
Example:
create table parent (id integer n
Hi,
I noticed that when an action is executed on a parent table, rules for that
action that are defined on its child tables are ignored.
Example:
create table A (ind integer);
create table B () inherits (A);
CREATE OR REPLACE RULE B_delete_rule AS
ON DELETE TO B DO INSTEAD NOTHING;
insert
> Alvaro Herrera writes:
> > Excerpts from depstein's message of lun jul 26 08:05:24 -0400 2010:
> >> I just want to note that one reason regclass may be used in user
> tables (as opposed to, say, regtype) is that in PL/pgSQL trigger
> procedures there is a special variable TG_RELID, which provide
> Bruce Momjian wrote:
> > depst...@alliedtesting.com wrote:
> > > I am trying to obtain a binary dump of a small test database where
> > > this issue could be reproduced, but so far, no luck. At present,
> the
> > > least such database is 1.5 GB compressed and contains a lot of
> > > proprietary i
I have encountered another problem with pg_upgrade, while migrating from 8.4 to
9.0 (beta2, as well as beta3) on Windows XP Pro.
I have a table with a regclass column, which references other tables in the
same database:
CREATE TABLE common_inst.reg_asset
(
asset_id integer NOT NULL,
table_n
PostgreSQL 8.4
Here is a PL/pgSQL procedure:
CREATE OR REPLACE FUNCTION select_test()
RETURNS void AS
$BODY$
DECLARE
id integer = -1;
BEGIN
select max(id) into id from test_table;
END
$BODY$
LANGUAGE 'plpgsql' VOLATILE
COST 100;
test_table is some table with an integer column 'id'.
The ab
Encountered another problem with pg_upgrade on Windows XP Pro:
I was trying to migrate from 8.4 to 9.0beta2 without linking, and apparently
there was not enough space on the hard drive. However, pg_upgrade didn't report
any problems, and it looked for all the world as if everything went well. I
Another issue:
4. The --link option doesn't seem to work on Windows: pg_upgrade still copies
data from the old cluster to the new. There doesn't appear to be a way to
upgrade a database on Windows without copying the entire uncompressed database,
which can be a problem where disk space is limit
PostgreSQL 9.0 beta 2
Windows XP Professional SP2
While migrating the database from 8.4 to 9.0 using pg_upgrade (now part of the
Postgres project), the following issues came up:
1. When using the --logfile option, pg_upgrade quits with an error like this:
The process cannot access the file beca
14 matches
Mail list logo