The following bug has been logged online:
Bug reference: 2717
Logged by: Pavel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Linux Redhat
Description:performance problem with enable_bitmapscan
Details:
Hi,
i have a following
The following bug has been logged online:
Bug reference: 2716
Logged by: Pavel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Linux Redhat
Description:performance problem with enable_bitmapscan
Details:
Hi,
i have a following
The following bug has been logged online:
Bug reference: 2324
Logged by: Pavel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP
Description:OLE DB Provider error
Details:
I have troubles/errors with the PostgreSQL OLE DB
s=# insert into g1(c) VALUES ('ahoj');
INSERT 0 1
postgres=# select * from g1;
a | c
---+--
t | ahoj
(1 row)
regards
Pavel Stehule
2008/7/26 Jeff Galyan <[EMAIL PROTECTED]>:
>
> The following bug has been logged online:
>
> Bug reference: 4324
> Logged
CTION
postgres=#
postgres=# SELECT to_ascii(convert_to('Příliš žlutý kůň', 'latin2'),'latin2');
to_ascii
--
Prilis zluty kun
(1 row)
postgres=# SELECT
to_ascii(convert_to('école','LATIN9'),'LATIN9');
to_ascii
--
W server_encoding;
server_encoding
-
UTF8
(1 row)
Encoding have to be same like encoding used in locales. If not, then
functions upper, lower doesn't work.
regards
Pavel Stehule
> the result is this:
> Xxx XXX öÖöÖäÄäÄä öÖöÖäÄäÄä
>
> Hope this h
, which are not evident from your
> description.
>
This bug was reported I though. win installer doesn't recognize
installed Perl 5.10 and doesn't allow plperl installation.
Pavel
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your s
Hello
PostgreSQL doesn't know username "sa". Same role is "postgres" in PostgreSQL.
What is your operation system?
regards
Pavel Stehule
p.s. it isn't bug, so mail to mailing list general -
http://www.postgresql.org/mailpref/pgsql-general
2008/8/25 Janar
2008/8/25 Janardhanachari, Jagadeesha <[EMAIL PROTECTED]>:
> What is the password for postgres ?
You filled it on win platforms, on unix platform this password isn't
filled. Try to login as system user postgres, then open local connect
to postgresql and then you can change pa
ure anyhow. Given the
> definitional issues involved with multiple SRFs in the same targetlist,
> putting more effort into the feature doesn't seem like a great
> investment of time.
I dislike this feature - sometime we can do nice hack with it, but
it's very dificult readabl
;t_func" () RETURNS SETOF "t_table" AS
postgres-# $body$
postgres$# DECLARE
postgres$# rec record;
postgres$# BEGIN
postgres$# FOR rec IN
postgres$# SELECT *
postgres$# FROM t_table
postgres$# WHERE 1=0
postgres$# LOOP
postgres$# RETURN NEXT rec;
postgres$# END LOOP;
postgres$# END;
post
t; buggy_enum_fieldNOTICE: drop cascades to table bug_table column
> buggy_enum_field
> ERROR: structure of query does not match function result type
> CONTEXT: PL/pgSQL function "buggy_procedure" line 3 at RETURN QUERY*/
this isn't bug, it's feature. Informations sto
3/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-DIAGNOSTICS
>
> RETURN isn't one of them.
>
>regards, tom lane
>
It should be enhanced - my initial proposal of return query expected
so return query is last statement, that isn't now. So we could ad
2008/11/6 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 2008/11/6 Tom Lane <[EMAIL PROTECTED]>:
>>> RETURN isn't one of them.
>
>> It should be enhanced - my initial proposal of return query expected
>&
I am sending patch, that adds FOUND and GET DIAGNOSTICS support for
RETURN QUERY statement
Regards
Pavel Stehule
2008/11/10 Andrew Gierth <[EMAIL PROTECTED]>:
>>>>>> "Pavel" == "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>
> >>
: 10
INSERT 0 1
regards
Pavel Stehule
2008/12/10 Oleg Serov <[EMAIL PROTECTED]>:
> SQL:
>
> CREATE OR REPLACE FUNCTION "bug_with_triggers" () RETURNS trigger AS
> $body$
> BEGIN
>PERFORM COALESCE(NEW.some_composite_field.field, TRUE);
> END;
> $
t; $body$
> DECLARE
>row_main_table main_type%rowtype;
> BEGIN
>row_main_table.subtype := NULL; -- all okey;
>row_main_table.subtype.flag := FALSE; -- cannot set
try
(row_main_table.subtype).flag := FALSE; -- cannot set
regards
Pavel Stehule
> END
; Kirill
two years ago I tested 5 users without problems. Try to vacuum and
reindex your system tables
regards
Pavel Stehule
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-
Really, this view is strange. I'll look on at
Pavel
2008/12/25, Kirill Simonov :
> Pavel Stehule wrote:
>> 2008/12/25 Kirill Simonov :
>>> Tom Lane wrote:
>>>> "Kirill Simonov" writes:
>>>>> It takes about 5 minutes to perform the q
Hello
really it's should be slow, it's cross join pg_class, pg_authid, pg_authid
for fast respond you have to specify minimally table_name and grantor fields.
select * from information_schema.table_privileges where table_name =
'foo' and grantor = 'pavel';
reg
t initalize.
initdb is one postgresql installed application
http://www.pgsql.cz/index.php/Instalace_PostgreSQL#Instalace_v_Microsoft_Windows
regards
Pavel Stehule
pripadne jsem na icq
>
>
>
> Thanks
>
>
>
> Tom Dixa
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
END IF;
RETURN QUERY some_other;
RETURN;
regards
Pavel Stehule
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
2009/1/10 Heikki Linnakangas :
> Pavel Stehule wrote:
>>
>> My first patch expected so RETURN QUERY is final statement, so I don't
>> solve FOUND variable, but Heikki changed this behave.
>
> Me? I don't recall doing anything related to this.
>
I have
lan=0x883b114, sourceText=0x883945c
"update t set d = d;", params=, dest=0x883b190,
completionTag=0xbfa8611a "") at pquery.c:196
#11 0x08264877 in PortalRunMulti (portal=0x887e91c, isTopLevel=, dest=0x883b190, altdest=0x883b190,
completionTag=0xbfa8611a "") at pq
only works when the INSERT is at
> the start of the statement :-(. Guess we need to change that.
>
> In the meantime, you can probably work around this by using EXECUTE,
> ie
>
We should ignore INTO keyword when statement starts with CREATE
keyword. This patch have to simple. I'
2009/2/2 Tom Lane :
> Pavel Stehule writes:
>> We should ignore INTO keyword when statement starts with CREATE
>> keyword. This patch have to simple. I'll prepare it.
>
> I'm already on it...
>
> regards, tom lane
ok
Reg
Hello
this limit will be removed at 8.4
in older version you have to use table notation like
select * from srf()
regards
Pavel Stehule
2009/2/10 Daniel Migowski :
> Hello dear PostgreSQL developers,
>
> I noticed the following strange behaviour with set-returning functions. If
&
The following bug has been logged online:
Bug reference: 4662
Logged by: Pavel Golub
Email address: pavel.go...@gf.microolap.com
PostgreSQL version: 8.4
Operating system: Windows XP SP3
Description:make failed using MinGW under WinXP
Details:
$ make
We got an
Hello
it's not bug,
8.1 doesn't support RETURNING clause
http://www.postgresql.org/docs/8.1/static/sql-insert.html
please, upgrade to current stable release (8.3)
regards
Pavel Stehule
2009/3/14 Brad Constantinescu :
>
> The following bug has been logged online:
>
> Bu
4662
PG> Logged by: Pavel Golub
PG> Email address: pavel.go...@gf.microolap.com
PG> PostgreSQL version: 8.4
PG> Operating system: Windows XP SP3
PG> Description:make failed using MinGW under WinXP
PG> Details:
PG> $ make
PG> We got an error:
PG>
$
SELECT
tst.id,
tst.vl
FROM tst;
END
$body$
LANGUAGE 'sql'
IMMUTABLE
CALLED ON NULL INPUT
SECURITY DEFINER
COST 1000 ROWS 1000;
regards
Pavel Stehule
2009/4/26 Alex :
>
> The following bug has been logged online:
>
> Bug reference: 4783
> Logge
Hello
you have to do vacuum full cerber.cerber_account
regards
Pavel Stehule
2009/5/8 Michal Szymanski :
> Hi,
> We call DB procedure that select rows with given ID it works as simple
> SELECT but for future changes we implement as DB procedure (look below
> for DB listing).
an help to migrate more people from mysql to postgreSQL
--
With best wishes,
Pavel mailto:pa...@gf.microolap.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Hello
this is known bug - you have to drop modified table and create it
again. I believe so this should be fixed early - in this summer.
regards
Pavel Stehule
2009/7/10 Sergey Burladyan :
> Alvaro Herrera writes:
>
>> Michael Tenenbaum wrote:
>>
>> > If I have a stor
by 1));
median
114
(1 row)
tested on pagila database
regards
Pavel Stehule
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>
--
Sent via
Hello
there is fix for bug Re: [BUGS] BUG #4907: stored procedures and changed tables
regards
Pavel Stehule
2009/7/10 Sergey Burladyan :
> Sergey Burladyan writes:
>
>> Alvaro Herrera writes:
>>
>> > Michael Tenenbaum wrote:
>> >
>> > > If
both tupdescs.
>>>
>>
>> ah! ok, i see... i will mark the patch as "waiting on author" and then
>> will try to fix it myself unless pavel wants to do it himself
>>
>
> patch attached
>
super, thanks
Pavel
>
> --
> Atentamente,
> Jaim
ion. But if you need it, then you can use
http://plsh.projects.postgresql.org/
I don't know if there is some similar project on window, but it's not
hard to write custom function in C and wrap exec system call. On
windows you can use plperlu and call external app from it.
regards
2009/7/28 Robert Haas :
> On Tue, Jul 28, 2009 at 1:19 PM, Jaime
> Casanova wrote:
>> On Tue, Jul 28, 2009 at 12:12 PM, Robert Haas wrote:
>>>>>
>>>>> patch attached
>>>>>
>>>> super, thanks
>>>>
>>>> Pav
e another routine that does that --- probably using a
> mapping data structure set up by validate_tupdesc_compat, since in some
> of these cases we'll be processing many tuples. Then the callers just
> have to know enough to call the tuple-translation function when
> validate_tupdes
There is fixed patch. Please, Jaime, can you look on it?
Thank You
Pavel
2009/7/30 Tom Lane :
> Jaime Casanova writes:
>>> On Mon, Jul 20, 2009 at 10:09 AM, Alvaro
>>>> Getting rid of the check on natts was "ungood" ... it needs to compare
>>>> th
2009/8/20 Dmitry Samokhin :
>
> The following bug has been logged online:
>
> Bug reference: 4997
> Logged by: Dmitry Samokhin
> Email address: s...@mail.ru
> PostgreSQL version: 8.3.7
> Operating system: Windows 2003 Server
> Description: Expression evaluation rules
> D
x27;UPDATE' OR TG_OP = 'DELETE' THEN
EXECUTE 'CASE WHEN $1 = 'DELETE' THEN true ELSE $2.a <> $3.a END'
USING TG_OP, OLD.a, OLD.b INTO result;
IF result THEN
RAISE NOTICE 'OK!';
Regards
Pavel Stehule
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
setof test as $$
declare _r record;
begin
for _r in execute 'select * from test where ' || quote_ident(_name)
|| ' is null'
loop
return next r;
end loop;
return;
end;
$$ language plpgsql;
regards
Pavel Stehule
>
> --
> Sent via pgsql-bugs mailing li
our database is unsecured!!!). Reload, then you can
login to database as postgres - password will be ignored.
execute SQL: ALTER USER postgres PASSWORD 'newpaswd';
change authentication back for local (ident or md5)!!!! reload
regards
Pavel Stehule
> Thanks for your hel
e, that null::foo and (null,
>> null)::foo should not be distinct.
>
> The more awkward case (to me anyway) is that the standard says (1,NULL)
> IS NULL should evaluate to TRUE.
what?
only (NULL, NULL) IS NULL is true
regards
Pavel Stehule
p.s. what isn't consistent (maybe - th
2009/9/1 Sam Mason :
> On Mon, Aug 31, 2009 at 07:26:59PM +0200, Pavel Stehule wrote:
>> 2009/8/31 Sam Mason :
>> > The more awkward case (to me anyway) is that the standard says (1,NULL)
>> > IS NULL should evaluate to TRUE.
>>
>> what?
>>
>&g
Hello
it's not bug - PostgreSQL doesn't support parameter placeholder on
this position. Use dynamic query instead - plpgsql statement EXECUTE.
regards
Pavel Stehule
2009/9/3 Keith Cascio :
>
> The following bug has been logged online:
>
> Bug reference: 5032
>
2009/9/3 Keith Cascio :
> Pavel,
>
> On Thu, 3 Sep 2009, Pavel Stehule wrote:
>
>> it's not bug - PostgreSQL doesn't support parameter placeholder on this
>> position. Use dynamic query instead - plpgsql statement EXECUTE.
>
> Thank you for your reply. I
2009/9/3 Robert Haas :
> On Sep 2, 2009, at 11:27 PM, Pavel Stehule wrote:
>
>> Hello
>>
>> it's not bug - PostgreSQL doesn't support parameter placeholder on
>> this position. Use dynamic query instead - plpgsql statement EXECUTE.
>
> It may not be
postgres=# explain select * from pg_class where relname='aaa';
QUERY PLAN
-
Index Scan using pg_class_relname_nsp_index on pg_class (cost=0.00..8.27 rows=
1 width=18
2009/9/7 Pavel Stehule :
> Hello
>
> 2009/9/7 Tomasz Karlik :
>>
>>
>>>>> Alvaro Herrera 9/4/2009 7:23 PM >>>
>> tkar...@ultimo.pl wrote:
>>
>>> Without casting function executes much slower:
>>>
>>> CREATE OR REP
ike plpgsql function?
regards
Pavel Stehule
2009/9/8 Martin Edlman :
>
> The following bug has been logged online:
>
> Bug reference: 5043
> Logged by: Martin Edlman
> Email address: edl...@fortech.cz
> PostgreSQL version: 8.2.0
> Operating system: Lin
ON
> schemebind. So the trigger deletes the '2009-09-01' record,
> get_schemebind_date() then returns correct result '2008-11-01'. But
> xfunc() then fails and the trigger operation is rolled back and I see
> the '2009-09-01' record again...
> Sorry guys for bother
tion
> Details:
>
> Upgrade from 8.1.15 -> 8.3.8
> lower(text) for Estonian characters don't work any more.
> Server encoding - LATIN9
> Client encoding - LATIN9
> On 8.1.15 it worked.
>
Hello
did you initialize database with correct locale?
Regards
Pavel Ste
QL,
T-SQL). But PostgreSQL supports plpgsql, plperl, plpython as sql
procedures - and I am sure, so standard doesnt calculate with
multilangual environments.
Regards
Pavel Stehule
Do you mean it can never
> be for some reason ? How about a simple function ?
>
> Thank you,
> Timot
2009/10/25 Timothy Madden :
>
> On Sun, Oct 25, 2009 at 6:17 PM, Pavel Stehule
> wrote:
>>
>> 2009/10/25 Timothy Madden :
>> >
>> >
>> > On Sun, Oct 25, 2009 at 12:42 PM, Peter Eisentraut
>> > wrote:
>> >>
>> >>
already, would probably
>> represent about 1% of the work needed to implement what the spec
>> suggests.
>
>
> I would like to put to good use the statements and expression that do match
> (SELECT/INSERT/UPDATE/ ...), and the very function declaration syntax is
> getting
rn v; end; $f$;
> CREATE FUNCTION
>
This isn't bug - it is just feature. ROW value cannot contain scalar
value. If you would to like reset variable, use NULL row constant.
BEGIN
v := (NULL, NULL);
-- it is equalent to NULL
RAISE NOTICE 'IS IT NULL %', v IS NULL;
RET
2009/11/1 Andrew Gierth :
>>>>>> "Pavel" == Pavel Stehule writes:
>
> >> As discussed on the irc. I had a problem with a utility function
> >> that was being passed a NEW row and a null for the OLD row. The
> >> error was created
|
user_defined_type_catalog|
user_defined_type_schema |
user_defined_type_name |
is_insertable_into | YES
is_typed | NO
commit_action
Regards
Pavel Stehule
>
> If anybody find it good please report it in my mail ID.
>
> Your reply is highly soli
ave process external variables first and then execute query.
Regards
Pavel Stehule
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
2009/11/16 Peter Eisentraut :
> On mån, 2009-11-16 at 10:19 +0100, Pavel Stehule wrote:
>> wrong:
>>
>> pa...@nemesis ~]$ psql postgres -v x=10 -c "select :x"
>> ERROR: syntax error at or near ":"
>> LINE 1: select :x
>>
2009/11/18 Peter Eisentraut :
> On mån, 2009-11-16 at 12:28 +0100, Pavel Stehule wrote:
>> 2009/11/16 Peter Eisentraut :
>> > On mån, 2009-11-16 at 10:19 +0100, Pavel Stehule wrote:
>> >> wrong:
>> >>
>> >> pa...@nemesis ~]$ psql postgres -
/Automatic_execution_plan_caching_in_PL/pgSQL
Regards
Pavel Stehule
p.s. this isn't bug - please use pg_general mailing_list
2009/11/19 Valaki Valahol :
> Dear Sirs,
>
> My name is Zoltán Ötvös and I'm from Hungary.
> Im using PostgreSQL database server from many years and I'm very satisfied
&g
x-MySQL people will be happy with SHOW support, then they will be
dissatisfied for PostgreSQL user's rights.
p.s. super hook should be useful not only for mysql's statement
regards
pavel
> ...Robert
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
&g
2009/11/30 Robert Haas :
> On Mon, Nov 30, 2009 at 12:28 PM, Pavel Stehule
> wrote:
>>>
>>> Rather than trying to be compatible with MySQL directly, I think we
>>> might be better off adding a chapter to our documentation explaining
>>> to ex-MySQL
2009/11/30 Tom Lane :
> Pavel Stehule writes:
>> I thing so ex-MySQL needs exact DESCRIBE, exact SHOW statement. It is
>> some, what they used long time and then they missing it.
>
> You know, if they're not willing to make any adaptations, they're never
> r
2009/11/30 Robert Haas :
> On Mon, Nov 30, 2009 at 1:42 PM, Pavel Stehule
> wrote:
>> 2009/11/30 Tom Lane :
>>> Pavel Stehule writes:
>>>> I thing so ex-MySQL needs exact DESCRIBE, exact SHOW statement. It is
>>>> some, what they used long time a
e a some hardware problems. Try to check your hardware,
please. Minimum is memory test.
Regards
Pavel Stehule
> Recently a new error appeared:
>
> Dec 13 03:46:55 goldbolt postgres[18628]: [15-1]
> user=randir,db=lovehunter ERROR: XX000: tuple offset out of range: 0
> Dec 13 03:46:5
s an alternative.
> Fortunately this is all handled through Hibernate, and so for now I have
> wrapped the substr command in rpad which seems to do the trick.
>
> Any light you can shed on this issue would be much appreciated.
>
Function substr has first parameter of type "t
2010/1/13 Pavel Stehule :
> Hello
>
> 2010/1/13 Charles O'Farrell :
>> Hi guys,
>>
>> I'm not sure whether this a really dumb question, but I'm curious as to what
>> might be the problem.
>>
>> We have a column 'foo' which is
se CREATE TABLE is DDL
statement without plan, and without possibility to use a parameters.
You have to do:
EXECUTE 'SELECT * FROM ' || var1::regclass || ' WHERE col=10' --
var1::regclass is minimum protection against SQL injection
EXECUTE 'CREATE TABLE '|| quote_ident(va
2010/1/14 Vincenzo Romano :
> 2010/1/14 Pavel Stehule :
>> Hello
>>
>> it is not bug.
>>
>> DDL statements like CREATE TABLE, ALTER TABLE are doesn't support
>> parametrisation - you cannot use a placeholder for parameter
>> everywhere. So you
> Pavel,
> if it was a simple plain dynami statement, I could create it by string
> concatenation, literal_ and ident_ quoting and so on.
the situation isn't too simply like you see it. PostgreSQL supports
composite and nested types. For this types you cannot use quote*
functions. N
1: select * from foo;
^
postgres=# select * from Foo;
ERROR: relation "foo" does not exist
LINE 1: select * from Foo;
^
postgres=# select * from "Foo";
a
---
(0 rows)
Time: 1,277 ms
you cannot change this behave. Just don't use doub
sql;
CREATE FUNCTION
Time: 18,734 ms
postgres=# select f();
ERROR: query returned no rows
CONTEXT: PL/pgSQL function "f" line 1 at SQL statement
postgres=#
regards
Pavel Stehule
>
> SELECT msg_id INTO v_nm FROM newmail WHERE memb_id=v_id;
>
> The only way to avoid the compl
2010/2/24 Josh Berkus :
> Pavel, all:
>
> Apparently if you use one returns table function to call a 2nd returns
> table function, it returns a recordset which consists entirely of nulls.
>
> Here's the test case:
>
> create table srf_data ( id serial, cat int, val t
xample as the reason we had
> to change the behavior ...
yes - I am very happy with this change. It is the biggest change in
plpgsql over 10 years.
Pavel
>
> --Josh Berkus
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscrip
because its actual rowtype is unspecified by the function text.
> The implications for row-null handling aren't obvious though :-(
>
is it necessary definition there? This is defined well from context.
regards
Pavel Stehule
> regards, tom lane
>
>
Hello
it's not bug. You registered plpgsql inside template1 database.
Regards
Pavel Stehule
2010/3/16 beulah prasanthi :
> hello
>
> I deleted existing DB and i created new DB
> i am getting below error how can i resolve it can any one help please
>
> "langu
Hello
It works on my server. Do you have a some specific configuration?
postgres=# select ('true'::text)::bool;
bool
--
t
(1 row)
I am checked 8.3, 8.4, 9.0.
Regards
Pavel Stehule
2010/3/18 Laczi József :
> I think this is a funny bug:
>
> select ('TR
rcecode column returns
0, which is wrong. Who can ever imagine bpchar of length 0? :)
(http://www.postgresql.org/docs/8.4/static/libpq-exec.html#LIBPQ-EXEC-SELECT-INFO)
--
With best wishes,
Pavel mailto:pa...@gf.microolap.com
--
Sent via pgsql-bugs mailing list (pgsql
Postgres.
>
> Am I doing something wrong, or is this really a bug?
probably you use old pgAdmin without support DEFAULT values :(.
Please, try to actualise your pgAdmin.
Regards
Pavel Stehule
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes
roisagg THEN 'agg'
WHEN p.proiswindow THEN 'window'
WHEN p.prorettype = 'pg_catalog.trigger'::pg_catalog.regtype THEN 'trigger'
ELSE 'normal'
END as "Type"
FROM pg_catalog.pg_proc p
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = p.pronamespace
treated as unqualified CHAR without an explicit length, with the further
> problem reported by Pavel of being treated as unlimited length instead of
> equivalent to CHAR(1) as expected. In other words, it seems to be effectively
> impossible to declare explicit lengths for RETURNS TABLE
onishment quotient.
I think, so RETURNS TABLE can be modified for returning typmode
without significant problems - this function is called in table
context and I don't see any problematic use case.
Pavel
>
>> I do think Pavel G. has a real bug with the char thing, though.
>
>
Hello, Tom.
You wrote:
TL> Pavel Golub writes:
>> Example:
>> CREATE OR REPLACE FUNCTION test_char_function()
>> RETURNS TABLE(id int, salesourcecode character) AS
>> $BODY$
>> VALUES (1, 'one'), (2, 'two'), (3, 'three');
>&
2010/4/15 Tom Lane :
> Pavel Stehule writes:
>> I think, so RETURNS TABLE can be modified for returning typmode
>> without significant problems - this function is called in table
>> context and I don't see any problematic use case.
>
> RETURNS TABLE is just a short
The following bug has been logged online:
Bug reference: 5451
Logged by: Pavel Golub
Email address: pa...@microolap.com
PostgreSQL version: 8.4.x
Operating system: Windows
Description:pg_restore doesn't close input .tar archive
Details:
pg_restore doesn&#x
Hello, Tom.
You wrote:
TL> "Pavel Golub" writes:
>> pg_restore doesn't close input .tar archive file after restore process.
>> However, file is closed after pg_restore termination, I suppose it's not
>> correct behaviour.
TL> I'm not sure wha
Hello, Tom.
You wrote:
TL> Pavel Golub writes:
>> TL> I'm not sure what distinction you're trying to draw. Do you want us to
>> TL> add a close() just before exit()? If so, what for?
>> First of all, for uniformity I guess. :) .backup files are closed
>
ed datatype.
Regards
Pavel Stehule
>
> the following is from the ecmascript 5 specification at
> http://www.ecmascript.org/docs/tc39-2009-043.pdf page 168:
>
>> 15.9.1.15 Date Time String Format
>> ECMAScript defines a string interchange format for date-times based upon a
The following bug has been logged online:
Bug reference: 2570
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.x
Operating system: Windows XP
Description:Connection closed unexpectedly
Details:
Bug may be reproduced by any tool using
The following bug has been logged online:
Bug reference: 2675
Logged by: Pavel Schon
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Debian Sarge, Linux 2.6.17.11 SMP i686 GNU/Linux
Description:syntax error
Details:
[local
.1.0
8.2.0
--
With best wishes,
Pavel mailto:[EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
The following bug has been logged online:
Bug reference: 2852
Logged by: Pavel Golub
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.x
Operating system: Windows XP
Description:User-defined type name begins with the underscore
character (_) can be created
t;shouldn't" be used, rather than prohibited.
BM> ---
BM> Pavel Golub wrote:
>>
>> The following bug has been logged online:
>>
>> Bug reference: 2852
>> Logged by:
r will ignore your desire to
B>choose an index scan if your joining column's datatypes do not
B>match
--
With best wishes,
Pavel mailto:[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: explain analyze is your friend
The following bug has been logged online:
Bug reference: 3056
Logged by: Pavel Stehule
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: Linux
Description:strange behave of CHECK constraint
Details:
Hello,
check constraint doesn't
1 - 100 of 277 matches
Mail list logo
