2013/10/4 Heikki Linnakangas
> On 02.10.2013 14:57,
> manindra.sarkar@brightnorth.**co.ukwrote:
>
>> Excel does not seem to respond with any data - but does give an idea that
>> it
>> has made some sort of a connection with the database. SQL commands fail
>> from
>> being executed.
>>
>
It is st
rays are
immutable - so any update is same as copy of array.
sometimes is better to generate table and build a array from table, but it
is not possible for two dimensional array without custom C extension :(
if you can, try to use PLPerl instead PL/pgSQL
You cannot do much more - for 1D arrays exi
Hello
it works on 9.1.9
postgres=# SELECT longlevenshtein(null, 'foobar');
longlevenshtein
-
6
Regards
Pavel
P.S. unlimitted varchar is "text" type in Postgres
2013/9/9
> The following bug has been logged on the website:
>
> Bug reference: 8441
> Logge
as
>> 0... lame.
>> I just wonder why it was working in the console, but it is not important -
>> at the moment it works just fine.
>>
>> Cheers,
>> Petr
>>
>> On 27.7.2013 22:59, Pavel Stehule wrote:
>>>
>>> Hello
>>>
>
.org/ftp/source/v7.4.30/ is probably last.
Regards
Pavel Stehule
> Problem is when multiple threads are accessing the postgresql database some
> times it is seen that, the database is getting crashed. Also we have seen
> the following error displayed:
>
>
> WARNING: terminating
Hello
2013/7/27 Andrew Gierth :
> Seems clearly your mistake to me... you do realize that (null + z) is
> always going to be null, right? Maybe your totals columns should have
> been declared NOT NULL (and presumably DEFAULT 0) to avoid this
> problem?
>
> Adding some diagnostics to your function
uot;z" ??
Please, you have to send a complete example in this case. Usually this
query is ook - and probably you have a problem with some interaction
PL/pgSQL | SQL
Regards
Pavel Stehule
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes t
reason for this behave is using a integer div in first case
( 1 / 2 ) * 3.2 ... 1/2 .. integer div, because left operand is int
and right operand is int
(3.2 * 1) / 2 ... 3.2 / 2 .. using numeric div, left operand is
numeric and right operand is int
Regards
Pavel Stehule
> Obviously both should
elations
Schema | Name | Type | Owner
+--+---+---
public | xx | table | pavel
xx | xx | table | pavel
(2 rows)
Regards
Pavel Stehule
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/m
2013/6/18 Andres Freund :
> On 2013-06-18 13:17:14 +, and...@lombardoni.ch wrote:
>> template1=# SELECT CASE WHEN 1=0 THEN 0 ELSE 1/0 END;
>> ERROR: division by zero
>>
>>
>> In this case the CASE behaves as expected.
>>
>>
>> But in the following expression:
>>
>>
>> template1=# SELECT CASE W
Hello
it is known old strange feature
http://postgresql.1045698.n5.nabble.com/Set-returning-functions-in-select-column-list-td5491544.html
Regards
Pavel Stehule
p.s. don't use this feature, it is strange - and we cannot change
behave due compatibility reasons.
2013/6/12 Denis de Ber
Hello
2013/2/21 Josh Kupershmidt :
> On Tue, Feb 19, 2013 at 6:00 AM, Pavel Stehule
> wrote:
>> 2013/2/16 Pavel Stehule :
>>> 2013/2/16 Tom Lane :
>>>> I think it has come up before. I wouldn't object to a pg_dump option to
>>>> add IF EX
2013/2/19 Peter Kroon :
>>try to use pgAdminIII
>
> Could you be more specific?
you can test your queries from pgAdmin SQL executor
but it is strange error - try to look to postgresql and system logs
Pavel
>
>
> 2013/2/19 Pavel Stehule
>>
>> 2013/2/19 Peter K
2013/2/19 Peter Kroon :
> Where can I check and/or alter this?
try to use pgAdminIII
Regards
Pavel
>
>
> 2013/2/19 Lou Picciano
>>
>> I wonder if there's a difference in the implementation(s) of readline
>> buffering?
>>
>>
>> - Original Message -
>> From: Peter Kroon
>> To: Lou Picci
Hello
2013/2/16 Pavel Stehule :
> 2013/2/16 Tom Lane :
>> Bruce Momjian writes:
>>> On Fri, Feb 15, 2013 at 04:06:12PM -0600, Dave Rolsky wrote:
>>>> Fair enough. It should probably an option to add "if exists", at
>>>> least. I can
e past.
>
> I think it has come up before. I wouldn't object to a pg_dump option to
> add IF EXISTS to all the drop commands (though changing the default
> behavior would be more controversial). Don't intend to spend my own
> time on it though ...
we use this feature m
Hello
this is not a bug report.
please, send your query to pg_general mailing list
probably better - ask on gridsql mailing list
Regards
Pavel Stehule
2013/2/5 :
> The following bug has been logged on the website:
>
> Bug reference: 7850
> Logged by: Nadir Va
2013/1/13 Andres Freund :
> On 2013-01-12 15:13:51 -0500, Tom Lane wrote:
>> Andres Freund writes:
>> > On 2013-01-12 14:29:38 -0500, Tom Lane wrote:
>> >> I think that the alternative most likely to succeed is to consider any
>> >> change in the active value of search_path as forcing replanning o
/
regards
Pavel Stehule
2013/1/3 :
> The following bug has been logged on the website:
>
> Bug reference: 7783
> Logged by: Alexander Shniperson
> Email address: alex.shniper...@gmail.com
> PostgreSQL version: 9.1.7
> Operating system: osx lion 10.7.5
> De
Hello
2012/12/12 Samrat :
> have a look at it if you find it usefull
> http://ora2pg-samrat.blogspot.in/
it is not a bug
please, use a different mailing list
Regards
Pavel Stehule
>
>
>
>
>
>
> --
> View this message in context:
> http://postgresql.10456
Hello
it is not a bug - it is known limit :(
nested structures are not supported as target
anybody can implement it if like it
Regards
Pavel Stehule
2012/11/29 :
> The following bug has been logged on the website:
>
> Bug reference: 7711
> Logged by: Michael
2012/11/23 Euler Taveira :
> On 22-11-2012 04:27, Pavel Stehule wrote:
>> 2012/11/21 Greg Sabino Mullane : Separately, what are
>> the objections to raising the size limit to 128?
>>
>>> significantly larger catalog
>>
> Less than 5% of catalog columns? I d
2012/11/21 Greg Sabino Mullane :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Gavin Flower asks:
>
>> Would it be appropriate to make it a WARNING in 9.2.2, then
>> increase the length in 9.3?
>
> No: revisions are reserved for bug fixes. This would be more of
> a behavior fix and a
f:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+COMMAND
> 2235 postgres 25 0 27.5g 23g4.6g R 95.175.231:39.81
> postgres: aspuser aspdata 10.0.2.67(52716) SELECT
>
>
> Radovan
>
> On Wed, Sep 26, 2012 at 10:15 PM, Pavel Stehule
>
me>=DATE('2012-09-26')
> test_db-# ORDER BY pnr_id ASC,nam_id ASC;
> ++----+-----+
> | pnr_id | nam_id | pty_num |
> +++-+
> | 1801 | 3359 | 1 |
> | 1801 | 3360 | 1 |
> | 1801 | 3361 | 1 |
> | 1801 | 3362 | 1 |
Hello
this situation is possible, when optimizer use HashAgg where should not use it.
Please, try to disable HashAgg - set enable_hashagg to off;
please, send EXPLAIN result
Regards
Pavel Stehule
2012/9/26 :
> The following bug has been logged on the website:
>
> Bug reference:
Hello
this is not bug - please, can you send your proposal to pg_hackers mailing list?
Regards
Pavel Stehule
2012/9/10 :
> The following bug has been logged on the website:
>
> Bug reference: 7529
> Logged by: Lego Haryanto
> Email address: legohar
t unnest($1)$$ language sql;
CREATE FUNCTION
postgres=# select un(1,2,3,4);
un
1
2
3
4
(4 rows)
postgres=# select un(variadic array[1,2,3]);
un
1
2
3
(3 rows)
A problem is in too simple evaluation of "any" parameter - without
check to "VARIADIC" flag
Regard
Hello
this is not bug - it is consequence of plan cache
http://postgres.cz/wiki/Automatic_execution_plan_caching_in_PL/pgSQL
please, use CURRENT_TIMESTAMP instead - using 'now'::timestamp is
deprecated due this issue
Regards
Pavel
2012/7/25 :
> The following bug has been logged on the websit
as this been reported as a bug in this version?
>
you index is broken - the source of this issue should be in hw or in sw.
Can you repeat a operations that breaks your indexes?
Regards
Pavel Stehule
>
>
>
>
>
> --
> View this message in context:
> http://postgresql
Please add built in feature in postgresql for setting size of individual
> table in terms of bytes ,megabyes etc. so that user wont be concerned about
> the data flooding out of disk.
>
> Thankyou, I hope you take this seriously.
>
>
this is not bug, but request feature
Regards
Pave
Hello
This is not bug
keyword EXCEPTION is supported only in plpgsql.
Regards
Pavel Stehule
2012/7/9 :
> The following bug has been logged on the website:
>
> Bug reference: 6724
> Logged by: Chine Bleu
> Email address: chine.b...@yahoo.com
> Postgre
2012/6/21 Rikard Pavelic :
> On 20.6.2012. 21:10, Tom Lane wrote:
>> rikard.pave...@zg.htnet.hr writes:
>>> create type t AS (i int); create type complex as (t t, i int); create table
>>> bad(i int, c complex); --This doesn't work as expected select * from bad
>>> where c is not null;
>> What do
2012/6/20 Rikard Pavelic :
> On 20.6.2012. 20:55, Pavel Stehule wrote:
>> Hello
>>
>> it is not a bug - see
>> http://archives.postgresql.org/pgsql-hackers/2009-07/msg01525.php
>>
>> Regards
>>
>> Pavel Stehule
>>
>
> I found that in d
Hello
it is not a bug - see
http://archives.postgresql.org/pgsql-hackers/2009-07/msg01525.php
Regards
Pavel Stehule
2012/6/20 :
> The following bug has been logged on the website:
>
> Bug reference: 6701
> Logged by: Rikard Pavelic
> Email address:
2012/5/22 Robert Haas :
> On Tue, May 22, 2012 at 3:55 PM, Tom Lane wrote:
>> Robert Haas writes:
deik3qfhu265n6=> with hello as (select 'hello' as name)
deik3qfhu265n6-> , bye as (select 'bye' as name)
deik3qfhu265n6-> select * from hello UNION ALL select * from bye;
ERROR:
2012/4/15 Boszormenyi Zoltan :
> 2012-04-14 18:15 keltezéssel, Peter Eisentraut írta:
>
>> On lör, 2012-04-14 at 08:23 -0400, Robert Haas wrote:
>>>
>>> On Sat, Apr 14, 2012 at 3:27 AM, Pavel Stehule
>>> wrote:
>>>>>
>>>>>
2012/4/14 Peter Eisentraut :
> On lör, 2012-04-14 at 08:23 -0400, Robert Haas wrote:
>> On Sat, Apr 14, 2012 at 3:27 AM, Pavel Stehule
>> wrote:
>> >> It has a lot of sense. Without it, it's very difficult to do logical
>> >> replication on a table
2012/4/14 Robert Haas :
> On Fri, Apr 13, 2012 at 10:43 PM, Pavel Stehule
> wrote:
>>> Yeah. I think it would be a good idea for UPDATE and DELETE to expose
>>> a LIMIT option, but I can't really see the virtue in making that
>>> functionality available
>
> Yeah. I think it would be a good idea for UPDATE and DELETE to expose
> a LIMIT option, but I can't really see the virtue in making that
> functionality available only through SPI.
>
I don't agree - LIMIT after UPDATE or DELETE has no sense. Clean
solution should be based on using updateable
2012/3/5 Tom Lane :
> Pavel Stehule writes:
>> Hello
>> I found a plpgsql bug:
>
>> create or replace function fx()
>> returns void as $$
>> declare a int; b int;
>> begin
>> select 10,20 into a;
>> end;
>> $$ language plpgsql;
>
Hello
I found a plpgsql bug:
create or replace function fx()
returns void as $$
declare a int; b int;
begin
select 10,20 into a;
end;
$$ language plpgsql;
this is bug, or minimally potential source of strange behave.
Regards
Pavel Stehule
--
Sent via pgsql-bugs mailing list (pgsql-bugs
check value of lc_collate variable
postgres=> show lc_collate;
lc_collate
-
en_US.UTF-8
(1 row)
different collations should have different order.
Regards
Pavel Stehule
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscripti
Hello
this is not bug
"OFFSET" doesn't mean go to line n - it means - first n lines don't
send to client.
Regards
Pavel Stehule
2012/2/22 :
> The following bug has been logged on the website:
>
> Bug reference: 6483
> Logged by: Kouber S
2012/1/4 Paul Ramsey :
> One extra detail, my PostgreSQL is compiled with --enable-cassert.
> This seems to be what sets off the killer function.
me too
Pavel
>
> On Wed, Jan 4, 2012 at 11:25 AM, hubert depesz lubaczewski
> wrote:
>> On Wed, Jan 04, 2012 at 07:17:17PM +, pram...@cleverelep
Hello
I can replicate it
postgres=# select kill_backend();
NOTICE: table "foo" does not exist, skipping
CONTEXT: SQL function "kill_backend" statement 1
The connection to the server was lost. Attempting reset: Failed.
!>
bash-4.2$ uname -a
Linux nemesis 2.6.41.4-1.fc15.x86_64 #1 SMP Tue Nov 29
uot;only ascii" user name, changing encoding
and changin current role
SET role TO specialcharsrole;
Regards
Pavel Stehule
2011/12/16 Pavel Holec :
> Hi All, please help.
>
> I Have PostgreSQL server 8.4.9 on Linux, database utf-8 and Client app on
> Windows (VC++ and libpq.d
e? Can you send a related SQL
statement, result from 9.0 and 8.4?
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
Hello
sorry, this is not bug, it is based on ispell dictionary behave
Regards
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
devel on i686-pc-linux-gnu, compiled by gcc (GCC) 4.5.1
20100924 (Red Hat 4.5.1-4), 32-bit
(1 row)
postgres=# show server_encoding;
server_encoding
─────
UTF8
(1 row)
postgres=# show lc_collate ;
lc_collate
─
cs_CZ.utf-8
(1 row)
Regards
Pavel Stehule
--
Sent via
2011/10/20 Tom Lane :
> Pavel Stehule writes:
>> I didn't design a PERFORM statement. There is two views - somebody
>> from sybase's family know so SELECT without into is forwarded to
>> client. This functionality is missing on Oracle's family. Is true so
&
ange, but maybe it's open door for sybase's
functionality that was not implemented ever.
Regards
Pavel Stehule
>
> regards, tom lane
>
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
2011/10/20 Merlin Moncure :
> On Thu, Oct 20, 2011 at 2:28 AM, Pavel Stehule
> wrote:
>>>
>>> it would be really a good idea to allow SELECT without INTO in plpgsql.
>>
>> SELECT without INTO is useless in plpgsql - because you have to drop result.
>
>
gards, tom lane
>>
>
> it would be really a good idea to allow SELECT without INTO in plpgsql.
SELECT without INTO is useless in plpgsql - because you have to drop result.
regards
Pavel Stehule
> PERFORM just makes things much more complicated, without actually adding any
it another way. Jan, do you
> remember anything about the reasoning for PERFORM?
>
It has a CALL statement, or procedures can be called directly.
Regards
Pavel Stehule
> regards, tom lane
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
2011/10/11 Tom Lane :
> Pavel Stehule writes:
>> I found a following issue (tested on PostgreSQL 9.2)
>
>> CREATE OR REPLACE FUNCTION public.setfield(a anyelement, text, text)
>> RETURNS anyelement
>> LANGUAGE plpgsql
>> AS $function$
>> beg
SQL statement "create temp table aux as select $1.*"
PL/pgSQL function "setfield" line 3 at SQL statement
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
6579
postgres=# select version();
version
──
PostgreSQL 9.2devel on x86_64-unknown-linux-gnu, compiled by gcc
(GCC) 4.6.0 20110603 (Red Hat 4.6.0-10), 64-bit
(1 row)
Time: 2,021
with two different instances of PG.
> Something being imported by plain DML operations?
> A strange idea by itself anyway.
>
> Still clueless...
>
> Rainer
>
>
> Am 17.08.2011 13:33, schrieb Pavel Stehule:
>> Hello
>>
>> 2011/8/17 Rainer Pruy :
>&g
; reported accordingly.
>
>
It is strange - are you sure, so UPDATE statement doesn't fail? Are
you sure, so UPDATE statement really modified rows?
Are you sure, so you are has not a broken index on PK?
Regards
Pavel Stehule
>
> Longer Version: please see text attachment
>
>
Hello
It working as expected on 9.0.4 Linux. Please, can you recheck your
application? Try to use a console - psql,
postgres=# select * from foo where date_to is null and date_to > '2011-01-01';
id | date_to
+-
(0 rows)
Regards
Pavel Stehule
2011/6/28 Renat :
>
) THEN
> RAISE NOTICE '%', a;
> END IF;
> RETURN;
> END;
> $$;
> ERROR: syntax error at or near "i"
> LINE 8: IF EXISTS (SELECT 1 INTO STRICT i) THEN
You cannot to use PLpgSQL's addition "INTO" inside SQL statement.
e for this
> language? I see that the last contrib was submitted years ago.
>
I worked on new implementation called PL/PSM - but it is not mature.
It should to work with 9.1.
https://github.com/okbob/plpsm0
all features https://github.com/okbob/plpsm0/blob/master/test.sql are
supported,
t;
> Yeah, it's not a very big concern, althougth cold be taken for future
> improvements
> in plpgsql. I very far for submit a patch :P
>
The deep check of embedded SQL is not possible in PL/pgSQL - this
remove dependency between PL/pgSQL and database objects. Deeper checks
mean a broken compatibility :(.
PL/PSM has different philosophy where full check is implemented now.
Regards
Pavel Stehule
> Regards,
> E
>
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
in INSERT
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
t;
>
>
> select oi.id from order_items oi INNER JOIN client_orders co ON oi.order_id
> = co.id
>
>
Do you do a ANALYZE and VACUUM. Can you send a result of EXPLAIN
ANALYZE SELECT ...
Please, do ANALYZE and VACUUM first.
regards
Pavel Stehule
>
> Regards,
>
> Nenea N
Hello
why you can do it?
please, try to RETURN QUERY ...
Regards
Pavel Stehule
>
> $$begin
>
> perform(
>
> with A as (select generate_series(1,3) as foo)
>
> select foo from A
>
> );
>
> end$$;
>
>
--
Sent via pgsql-bugs mailing list (pgsql-bu
nge you're talking about?
>
There is nothing similar in standard. Multirecordset is nice, but not
standard feature.
Regards
Pavel Stehule
> Regards,
> --
> Dimitri Fontaine
> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
>
> --
> Sent via pgsql-bu
> Sorry if I'm being dense, but I can't see how you can pass a tuple; I think
> raise-notice only lets you pass individual strings/integers. But I don't
> think we can pass all of them without specifying in advance how many there
> are....
yes, it's possible for ROW
debugging statement, then get back to the problem at hand, rather than
> having to break out of the current programming task to write a debug
> function :-)
>
CREATE OR REPLACE FUNCTION debug_query(text)
RETURNS void AS $$
DECLARE r record;
BEGIN
FOR r IN EXECUTE $1 LOOP
RAISE NO
2011/2/14 Kevin Grittner :
> Pavel Stehule wrote:
>
>> p.s. Using a case sensitive identifiers isn't good idea
>
> Is there any reason for that assertion besides the need to
> consistently quote them?
>
readability - and when you are started quoting, then you
','231'],
> ARRAY["time"('21:00:00'),"time"('16:25:00')],
> ARRAY['2:30','2:35']);
>
> now i want to execute this query:
> select "FlightNum[0]" FROM flight."FlightList";
>
> return this
2011/2/2 Tom Lane :
> Pavel Stehule writes:
>> probably you need a third form of expansion - not implemented yet
>> ":$$var$$
>
> Seems quite useless. A string literal is a string literal.
>
I don't propose this form now. I saying so this form can be usefull fo
Hello
probably you need a third form of expansion - not implemented yet
":$$var$$
escaping :'xxx' is designed for SQL language, not for Python :(
Regards
Pavel
2011/2/2 Steve White :
> Hi, Robert,
>
> On 1.02.11, Robert Haas wrote:
>>
>> Can't you already do it this way:
>>
>> \set yadda `ca
quot; account, then it is.
I don't think, so your idea is good too. What about caching? Code of
stored procedures stays in session cache. Who will ensure, so your
cache is fresh?
Why you need a direct link to source files?
Regards
Pavel Stehule
>
> If somehow loading script text for a
EXECUTE "xx"($1)
ERROR: there is no parameter $1 - but function is called with one parameter
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
ng ('') worked for me on pre-9.0 versions to get array of
> string chars. Now I have the following behavior:
Hello
it's newer worked like you remember
postgres=# select regexp_split_to_array('abc','');
regexp_split_to_array
---
Hello Marc,
It was entered from a windows cmd console? It doesn't use win
encodings as default. For example, it must be executed with parameter
/c chcp 1250 for win1250 encoding.
Regards
Pavel Stehule
2010/12/23 Marc Cousin :
>
> The following bug has been logged online:
>
&
which can be
> used in other processing. Of course, I've found another solution, but
> creating view with parameter dynamically could be a good feature.
>
It's done - SQL immutable function works exactly like you need.
Regards
Pavel Stehule
> Andrey
>
>
>
> 2010/12/14 P
Cond: (a = 10)
(2 rows)
Regards
Pavel Stehule
2010/12/13 Andrey G. :
> It seems my original test, which also includes the EXECUTE approach,
> has not come to you in full. EXECUTE statement also fails with
> parameter: The test is attached in file.
>
> psql -q < db/db/pgbug_5776.s
2010/12/10 Tom Lane :
> Pavel Stehule writes:
>> 2010/12/9 Tom Lane :
>>> What exactly is the use-case for that?
>
>> I am working on function that can help with record updating. It's
>> based on polymorphic types. I would to allow a multiple modification
&
2010/12/9 Tom Lane :
> Pavel Stehule writes:
>> I didn't explain it well, sorry
>
>> so I have a function foo(variadic "any")
>
>> usual calling like foo(10,20) or foo('a',10) working perfectly. But I
>> have a problem with call with VA
2010/12/9 Tom Lane :
> Pavel Stehule writes:
>> There is missing expansion for variadic parameter from any array to
>> real parameters when variadic type is "any".
>
> That's not a bug, it's intentional. Variadic any is intended to let the
> C functi
Hello
There is missing expansion for variadic parameter from any array to
real parameters when variadic type is "any".
It can be solved on C level, but in this moment we have not a access
to parser, so we don't know, if variadic flag was used or not.
Regards
Pavel Stehule
--
2010/11/16 vince maxey :
> Here is my website: www.emenusonline.net It appears that the pg version my
> web
> host company uses is 8.1.3
>
> Right now this site is in beta mode, so you can register and order food
> and there will be no repercussions, other than you will receive an email
> indica
postgres=# commit;
COMMIT
Regards
Pavel Stehule
>
> I have many years SQL development experience and work with Oracle in my
> current
> position. I'm not a novice programmer.
>
> My functions all worked prior to switching to 9.0 and I can excute functions
> from
2010/8/5 Tom Lane :
> Pavel Stehule writes:
>> but still when we remove one parametric string_agg, then this issue
>> will not be documented.
>
> How so? This paragraph will still be there:
>
>
> When dealing with multiple-argument aggregate functions, note
2010/8/5 Tom Lane :
> Pavel Stehule writes:
>>>>> The same problem can be with custom aggregates :( so this syntax isn't
>>>>> too robust.
>
> BTW, I'm really not worried about that case. By the time someone is
> advanced enough to have writ
2010/8/5 Tom Lane :
> Thom Brown writes:
>> On 5 August 2010 10:29, Greg Stark wrote:
>>> On Thu, Aug 5, 2010 at 5:18 AM, Pavel Stehule
>>> wrote:
>>>> The same problem can be with custom aggregates :( so this syntax isn't
>>>> too r
2010/8/4 Kevin Grittner :
> Alex Hunsaker wrote:
>> On Wed, Aug 4, 2010 at 11:04, Tom Lane wrote:
>>> If we were a bit earlier in the 9.0 cycle I would suggest that
>>> this confusion is a sufficient reason to drop the one-argument
>>> form of string_agg. It's too late now though.
>>
The same p
2010/8/4 Thom Brown :
> On 4 August 2010 14:24, Pavel Stehule wrote:
>> 2010/8/4 Thom Brown :
>>> On 4 August 2010 14:04, Robert Haas wrote:
>>>> On Wed, Aug 4, 2010 at 6:03 AM, Thom Brown wrote:
>>>>> Actually, this rings a bell. I think this may h
this isn't intuitive
and pg can do better diagnostic now. But it has a sense. ORDER BY
hasn't sense for one parameter - only for complete function, so is
wrong to write ORDER BY over a some interesting parameter
Regards
Pavel Stehule
>
> Thom
>
> --
> Sent via pgsql-bugs ma
Hello
your trigger is AFTER or BEFORE trigger? Because BEFORE trigger is
executed before new value is propagated to table.
Regards
Pavel Stehule
2010/7/23 Alessio :
>
> The following bug has been logged online:
>
> Bug reference: 5569
> Logged by: Alessio
reference "id" is ambiguous
LINE 1: select max(id) from test_table
^
DETAIL: It could refer to either a PL/pgSQL variable or a table column.
QUERY: select max(id) from test_table
CONTEXT: PL/pgSQL function "select_test" line 8 at SQL state
2010/5/31 Bruce Momjian :
> Pavel Stehule wrote:
>> 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
>> >
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
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
2010/4/15 Tom Lane :
> "Kevin J Bluck" writes:
>> But if RETURN TABLE doesn't respect typemods, perhaps it shouldn't be
>> legal to specify them in that clause?
>
> Yeah, possibly. CREATE FUNCTION has historically accepted (and then
> discarded) typmod information for all function parameter and r
character type
> columns.
>
> This doesn't happen with the RETURNS SETOF variation, only RETURNS TABLE.
>
> Regards,
RETURNS TABLE (x int, y int) is equal to CREATE FUNCTION foo(.. OUT x
int, OUT y int) RETURNS SETOF RECORD. But PostgreSQL functions ignore
typmod fo
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
1 - 100 of 228 matches
Mail list logo
