Alexsander Rosa wrote:
> At 8.4 release notes, item "E.5.3.3.1. TRUNCATE" there's a sentence:
> "The start value of a sequence can be changed by ALTER SEQUENCE START WITH.
> "
>
> Maybe this sentence should be copied/moved to "E.5.3.4.1. ALTER" with extra
> text stating that START, in previous ver
"Maxim Boguk" writes:
> All plan look reasonable for me except that part:
>-> Sort (cost=233.86..242.35 rows=3399 width=161) (actual
> time=15.138..26960.441 rows=19164919 loops=1)
> Sort Key: plan_s.tarif_id, plan_s.shortname
> Sort Method: quicksort Memory: 604kB
>
Well, if it's not going to be fixed, then at least the docs should be
revised to warn all 8.4+ users to avoid this command and, if it's really
needed, always check the server version before using the ALTER SEQUENCE ...
START command, once it has a potentially hazardous bug that interprets it as
a R
At 8.4 release notes, item "E.5.3.3.1. TRUNCATE" there's a sentence:
"The start value of a sequence can be changed by ALTER SEQUENCE START WITH.
"
Maybe this sentence should be copied/moved to "E.5.3.4.1. ALTER" with extra
text stating that START, in previous versions, was an (unintended) alias to
The following bug has been logged online:
Bug reference: 5649
Logged by: Maxim Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 8.4.4
Operating system: FreeBSD 7.2
Description:strange (probably bugged) explain analyze output
Details:
I not sure it is a
Alexsander Rosa wrote:
> Well, if it's not going to be fixed, then at least the docs should be
> revised to warn all 8.4+ users to avoid this command and, if it's really
> needed, always check the server version before using the ALTER SEQUENCE ...
> START command, once it has a potentially hazardou
Valentine Gogichashvili writes:
> CREATE TYPE ta AS (a1 integer, a2 text);
> CREATE TYPE tb AS (b1 integer, b2 ta);
> DECLARE
> a ta;
> b tb;
> BEGIN
> SELECT 1, 'a' INTO a; -- ok
> SELECT ROW(10, 'a') INTO b.b2; -- ok in 8.4 but fails in 9.0 [ERROR:
> invalid input syntax for integer
Sorry, did not check it exactly on the 8.4, now installed 8.4 and reproduced
the issue:
BEGIN;
CREATE TYPE ta AS (a1 integer, a2 text);
CREATE TYPE tb AS (b1 integer, b2 ta);
CREATE OR REPLACE FUNCTION public.foo()
RETURNS void
LANGUAGE plpgsql
AS
$DOIT$
DECLARE
a ta;
b tb;
BEGIN
RAISE I
