[BUGS] psql \i command with a missing file name doesn't rollback the transaction

2013-09-20 Thread Alexey Klyukin
te the rollback to the server on an attempt to include a non-existing file (perhaps only when ON_ERROR_STOP is set to 1?). -- Regards, Alexey Klyukin

Re: [BUGS] the '::' cast doesn't work in the FROM clause

2011-08-29 Thread Alexey Klyukin
work. Would it be acceptable/sufficient to output CAST(...) instead of '::' for all casts in pg_dump to fix this problem, assuming that CAST can be used anywhere where '::' is accepted? -- Alexey Klyukinhttp://www.commandprompt.com The PostgreSQL Company – Command Prompt, Inc. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] the '::' cast doesn't work in the FROM clause

2011-08-29 Thread Alexey Klyukin
On Aug 29, 2011, at 5:02 PM, Kevin Grittner wrote: > Alexey Klyukin wrote: > >> Function calls can appear in the FROM clause. (This is especially >> useful for functions that return result sets, but any function can >> be used.) This acts as though its output were c

Re: [BUGS] the '::' cast doesn't work in the FROM clause

2011-08-29 Thread Alexey Klyukin
On Aug 29, 2011, at 3:49 PM, Kevin Grittner wrote: > Alexey Klyukin wrote: > >> The following statement produces an error message in PostgreSQL 8.4 >> - 9.2 (head): >> >> postgres=# select val from random()::integer as val; > >> The same statement r

[BUGS] the '::' cast doesn't work in the FROM clause

2011-08-29 Thread Alexey Klyukin
casts are equivalent, so either that's wrong, or this is a bug. The target OS is Mac OS X 10.7.1 with llvm-gcc-4.2 used as a compiler. -- Alexey Klyukinhttp://www.commandprompt.com The PostgreSQL Company – Command Prompt, Inc. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgr

Re: [BUGS] BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message

2011-06-02 Thread Alexey Klyukin
On Jun 2, 2011, at 6:21 PM, Artiom Makarov wrote: > 2011/6/2 Alexey Klyukin : > >> What would you expect to happen for TRUNCATE .. CASCADE? >> >> One thing I find potentially surprising is that TRUNCATE CASCADE doesn't >> follow the semantics of 'ON DEL

Re: [BUGS] BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message

2011-06-02 Thread Alexey Klyukin
ause other objects depend on it > > SQL state: 2BP01 > Detail: table tr_test1 depends on schema public > table tr_test2 depends on schema public > table tr_test3 depends on schema public > Hint: Use DROP ... CASCADE to drop the dependent objects too. -- Alexey Klyukin The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] 9.1 plperlu bug with null rows in trigger hash

2011-05-27 Thread Alexey Klyukin
programmer. > >To avoid a backwards compatibility hit, the string representation of > each structure is also available if the function requests it. > >Authors: Alexey Klyukin and Alex Hunsaker. >Some code cleanups by me. > > Which also means it only b

Re: [BUGS] BUG #5323: plperl and plperlu interaction segfaults

2010-02-12 Thread Alexey Klyukin
On Feb 12, 2010, at 6:21 AM, Robert Haas wrote: > On Thu, Feb 11, 2010 at 10:47 PM, Robert Haas wrote: >> On Thu, Feb 11, 2010 at 3:12 PM, Alexey Klyukin >> wrote: >>>> I think this might be the same problem previously discussed here: >>>> http://arc

Re: [BUGS] BUG #5323: plperl and plperlu interaction segfaults

2010-02-11 Thread Alexey Klyukin
roblem previously discussed here: > > http://archives.postgresql.org/pgsql-bugs/2010-01/msg00224.php Seems to be the same problem. Backtrace I'm getting on 8.4 is almost identical to the one at the end of this post: http://archives.postgresql.org/pgsql-bugs/2010-01/msg00144.php > >