Re: [HACKERS] proposal: schema variables

Hi 2017-11-13 13:15 GMT+01:00 Pavel Golub <pa...@microolap.com>: > Hello, Pavel. > > You wrote: > > PS> Hi, > > PS> I propose a new database object - a variable. The variable is > PS> persistent object, that holds unshared session based not > PS> tr

Re: [HACKERS] proposal: schema variables

Hello, Pavel. You wrote: PS> Hi, PS> I propose a  new database object - a variable. The variable is PS> persistent object, that holds unshared session based not PS> transactional in memory value of any type. Like variables in any PS> other languages. The persistence is required

Re: [HACKERS] possible encoding issues with libxml2 functions

2017-11-11 21:19 GMT+01:00 Noah Misch <n...@leadboat.com>: > On Sun, Nov 05, 2017 at 06:10:04PM +0100, Pavel Stehule wrote: > > Hi > > > > 2017-11-05 4:07 GMT+01:00 Noah Misch <n...@leadboat.com>: > > > > > On Tue, Oct 17, 2017 at 06:06:40AM +0200,

Re: [HACKERS] proposal: psql command \graw

> topt logic should be reviewed, but that is not the point of this patch. > I don't think so it is not correct - this mean tuples only + header. Probably the best implementation is something three state - all, tuples only, tuples only and header. But it mean much more changes in psql logic - not adequate to size of this patch > So I switched the patch to "ready for committer". > Thank you very much Regards Pavel > > -- > Fabien. >

Re: [HACKERS] Variable substitution in psql backtick expansion

for commiters Regards Pavel diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index d360fc4d58..924766fce7 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -7956,8 +7956,22 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir

Re: [HACKERS] Transform for pl/perl

and returns it. > > create extension jsonb_plperl cascade; > > create or replace function test(val jsonb) > returns jsonb > transform for type jsonb > language plperl > as $$ > return $_[0]; > $$; > > select test('{"1":1,"example": null}'::jsonb); >

[HACKERS] pg audit requirements

be processed and logged in audit log too. Regards Pavel

Re: [HACKERS] proposal: psql command \graw

2017-11-10 8:12 GMT+01:00 Fabien COELHO : > > ISTM that you can remove "force_column_header" and just set "tuple_only" >>> to what you need, that is you do not need to change anything in function >>> "print_unaligned_text". >>> >> >> Last point is not possible - I would not

Re: [HACKERS] proposal: psql command \graw

2017-11-09 21:12 GMT+01:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-11-09 21:03 GMT+01:00 Fabien COELHO <coe...@cri.ensmp.fr>: > >> >> Hello Pavel, >> >> I hope so I fixed all mentioned issues. >>> >> >> Patch app

[HACKERS] different content of pg_depend after pg_upgrade

classid), objid from pg_depend group by objid; when system was loaded from dump but when we used pg_upgrade, then previous rule was invalid. Is it expected behave? Regards Pavel

Re: [HACKERS] proposal: psql command \graw

2017-11-09 21:03 GMT+01:00 Fabien COELHO <coe...@cri.ensmp.fr>: > > Hello Pavel, > > I hope so I fixed all mentioned issues. >> > > Patch applies with a warning: > > > git apply ~/psql-graw-2.patch > /home/fabien/psql-graw-2.patch:192: new blank

Re: [HACKERS] proposal: psql command \graw

Hi 2017-08-24 5:50 GMT+02:00 Fabien COELHO <coe...@cri.ensmp.fr>: > > Hello Pavel, > > I have added the patch to the next commitfest. > > Patch applies, compiles, works. > > I'm okay with the names graw/graw+, and for having such short-hands. > > Missin

Re: [HACKERS] proposal - Default namespaces for XPath expressions (PostgreSQL 11)

8 conflicts on doc/src/sgml/func.sgml > > > At Sun, 15 Oct 2017 12:06:11 +0200, Pavel Stehule <pavel.steh...@gmail.com> > wrote in <CAFj8pRCYBH+a6oJoEYUFDUpBQ1ySwtt2CfnFZxs2A > b9efon...@mail.gmail.com> > > 2017-10-02 12:22 GMT+02:00 Kyotaro HORIGUCHI < > > hor

Re: [HACKERS] SQL procedures

2017-11-08 15:31 GMT+01:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-11-08 15:23 GMT+01:00 Peter Eisentraut <peter.eisentraut@2ndquadrant. > com>: > >> On 10/31/17 16:50, Pavel Stehule wrote: >> > Not sure if disabling RETURN is good idea

Re: [HACKERS] SQL procedures

2017-11-08 15:23 GMT+01:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 10/31/17 16:50, Pavel Stehule wrote: > > Not sure if disabling RETURN is good idea. I can imagine so optional > > returning something like int status can be good idea. Cheaper than &g

Re: [HACKERS] possible encoding issues with libxml2 functions

Hi 2017-11-05 4:07 GMT+01:00 Noah Misch <n...@leadboat.com>: > On Tue, Oct 17, 2017 at 06:06:40AM +0200, Pavel Stehule wrote: > > Please, if you can, try it write. I am little bit lost :) > > I'm attaching the patch I desired. Please review. This will probably miss > th

Re: [HACKERS] proposal: schema variables

2017-11-02 13:35 GMT+01:00 Robert Haas <robertmh...@gmail.com>: > On Thu, Oct 26, 2017 at 12:51 PM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > > The variables can be modified by SQL command SET (this is taken from > > standard, and it natural) &g

Re: [HACKERS] proposal: schema variables

2017-11-02 16:07 GMT+01:00 Craig Ringer <cr...@2ndquadrant.com>: > On 26 October 2017 at 15:21, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > > Hi, > > > > I propose a new database object - a variable. > > Didn't we have a pretty long discussion

Re: [HACKERS] proposal: schema variables

2017-11-02 16:35 GMT+01:00 Nico Williams <n...@cryptonector.com>: > On Thu, Nov 02, 2017 at 06:05:54PM +0530, Robert Haas wrote: > > On Thu, Oct 26, 2017 at 12:51 PM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > > > The variables can be modified by SQ

Re: [HACKERS] SQL/JSON in PostgreSQL

ate "needs review". I looked to the patch, and found some issues, so I sent mail about these issues and switched state to "waiting on author" Regards Pavel > > -- > Peter Eisentraut http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services >

Re: [HACKERS] proposal: schema variables

bles like you know from PlpgSQL. But the holder is not the plpgsql function. The holder is a schema in this case. The variable (meta) is permanent. The content of variable is session based untransactional. Regards Pavel > mark >

Re: [HACKERS] [PATCH] Add two-arg for of current_setting(NAME, FALLBACK)

Hi better to send it as attachment Regards Pavel 2015-03-19 23:41 GMT+01:00 David Christensen <da...@endpoint.com>: > The two-arg form of the current_setting() function will allow a > fallback value to be returned instead of throwing an error when an > unknown GUC is provid

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

ch with some basic doc Regards Pavel > > -- > Alexander Korotkov > Postgres Professional: http://www.postgrespro.com > The Russian Postgres Company > diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index e520cdf3ba..7d816fe701 100644 --- a/doc/

Re: [HACKERS] Dynamic result sets from procedures

e result sets > fetch result > stop timer > foreach result set > print result > > but that would have a lot more overhead, potentially. > > Thoughts? > Has the total time sense in this case? should not be total time related to any fetched result? Rega

Re: [HACKERS] proposal: schema variables

ntation of global temp tables in Postgres. This temporary behave is marginal part of proposal - so I can to remove it from proposal - and later open discussion about CREATE TEMPORARY VARIABLE versus DECLARE VARIABLE Regards Pavel Serge >

Re: [HACKERS] proposal: schema variables

2017-10-31 22:28 GMT+01:00 srielau <se...@rielau.com>: > Pavel, > > There is no > DECLARE TEMP CURSOR > or > DECLARE TEMP variable in PLpgSQL > and > sure .. DECLARE TEMP has no sense, I talked about similarity DECLARE and CREATE TEMP CREATE TEMP TABLE has a

Re: [HACKERS] proposal: schema variables

2017-10-31 22:08 GMT+01:00 Serge Rielau <se...@rielau.com>: > Pavel, > > I can imagine, so DECLARE command will be introduced as short cut for > CREATE TEMP VARIABLE, but in this moment I would not to open this topic. I > afraid of bikeshedding and I hope so CREA

Re: [HACKERS] SQL procedures

orked with previously.) > Not sure if disabling RETURN is good idea. I can imagine so optional returning something like int status can be good idea. Cheaper than raising a exception. Regards Pavel > -- > Peter Eisentraut http://www.2ndQuadrant.com/ > PostgreSQL Dev

Re: [HACKERS] proposal: schema variables

Hi 2017-10-30 22:42 GMT+01:00 srielau <se...@rielau.com>: > Pavel, > > I wouldn't put in the DROP option. > Or at least not in that form of syntax. > > By convention CREATE persists DDL and makes object definitions visible > across sessions. > DECLARE defines sessio

Re: [HACKERS] SQL procedures

procedure bodies > > - Returning multiple result sets > > (In various previous discussions on "real stored procedures" or > something like that, most people seemed to have one of these two > features in mind. I think that depends on what other SQL systems one > ha

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

2017-10-28 23:35 GMT+02:00 Alexander Korotkov <a.korot...@postgrespro.ru>: > On Sat, Oct 28, 2017 at 3:46 PM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > >> 2017-09-22 21:31 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: >> >>> >

Re: [HACKERS] proposal: schema variables

Hi 2017-10-28 16:24 GMT+02:00 Chris Travers <chris.trav...@adjust.com>: > > > On Thu, Oct 26, 2017 at 9:21 AM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > >> Hi, >> >> I propose a new database object - a variable. The variable is persistent

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

Hi 2017-09-22 21:31 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-09-22 21:12 GMT+02:00 Peter Eisentraut <peter.eisentraut@2ndquadrant. > com>: > >> On 9/22/17 09:16, Pavel Stehule wrote: >> > Example: somebody set SORT_COLUMNS to schem

Re: [HACKERS] proposal: schema variables

2017-10-27 15:38 GMT+02:00 Gilles Darold <gilles.dar...@dalibo.com>: > Le 26/10/2017 à 09:21, Pavel Stehule a écrit : > > Hi, > > > > I propose a new database object - a variable. The variable is > > persistent object, that holds unshared session based not

Re: [HACKERS] inconsistency in process names - bgworker: logical replication launcher

2017-10-27 13:03 GMT+02:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 10/27/17 04:06, Pavel Stehule wrote: > > Why buildin process has prefix bgworker? > > Implementation detail. This has been changed in master already. > ok Thank you Pavel &

[HACKERS] inconsistency in process names - bgworker: logical replication launcher

(3114) idle 32274 ?Ss 0:00 postgres: ides ides_jmmaj_akt 192.168.1.50(3124) idle regards Pavel

Re: [HACKERS] proposal: schema variables

2017-10-27 7:47 GMT+02:00 Tsunakawa, Takayuki < tsunakawa.ta...@jp.fujitsu.com>: > From: pgsql-hackers-ow...@postgresql.org > > [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Pavel Stehule > > I propose a new database object - a variable. The variable is

Re: [HACKERS] proposal: schema variables

Hi 2017-10-27 0:07 GMT+02:00 Nico Williams <n...@cryptonector.com>: > On Thu, Oct 26, 2017 at 09:21:24AM +0200, Pavel Stehule wrote: > > Comments, notes? > > I like it. > > I would further like to move all of postgresql.conf into the database, > as much as poss

[HACKERS] proposal: schema variables

implicitly (without JOIN) SELECT varname; The SEARCH_PATH is used, when varname is located. The variables can be used everywhere where query parameters are allowed. I hope so this proposal is good enough and simple. Comments, notes? regards Pavel

Re: [HACKERS] pgbench - allow to store select results into variables

"eset" .. like embeded set? The code of append_sql_command is not too readable and is not enough commented. I don't understand why you pass a param compounds to append_sql_command, when this value is stored in my_command->compound from create_sql_command? Or maybe some unhappy field or variable names was chosen. Regards Pavel > > -- > Fabien.

Re: [HACKERS] pgbench more operators & functions

Hi 2017-10-20 18:36 GMT+02:00 Fabien COELHO : > > Here is a v13. No code changes, but TAP tests added to maintain pgbench coverage to green. >>> > Here is a v14, which is just a rebase after the documentation xml-ization. > all tests passed no problems with doc

[HACKERS] new field for structured exception - query

Hi Currently we don't allow a access to internalquery field from PLpgSQL via GET STACKED DIAGNOSTICS. Do you think so has sense to allow the access to this field? The patch can be very small. Regards Pavel

Re: [HACKERS] stalled post to mailing list - wrong filter?

2017-10-22 9:08 GMT+02:00 Magnus Hagander <mag...@hagander.net>: > > > On Sun, Oct 22, 2017 at 9:02 AM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > >> Hi >> >> I sent correct mail, that requires the approval - maybe bad filter? >> >

[HACKERS] stalled post to mailing list - wrong filter?

e number 4. If you do not wish the message to be posted, or have other concerns, please send a message to the list owners at the following address: pgsql-hackers-ow...@postgresql.org Regards Pavel

Re: [HACKERS] Interest in a SECURITY DEFINER function current_user stack access mechanism?

l 1 is "the previous current_user in the stack", and > so on, returning null when level is beyond the top-level. > > This seems like a simple, small, easy patch, and since I [think I] need > it I suspect others probably do as well. > > Thoughts? > there is a function session_

Re: [HACKERS] possible encoding issues with libxml2 functions

2017-10-17 1:57 GMT+02:00 Noah Misch <n...@leadboat.com>: > On Sun, Aug 20, 2017 at 10:37:10PM +0200, Pavel Stehule wrote: > > > We have xpath-bugfix.patch and xpath-parsing-error-fix.patch. Both are > > > equivalent under supported use cases (xpath in UTF8 databases).

Re: [HACKERS] possible encoding issues with libxml2 functions

2017-08-21 6:25 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > >> xpath-bugfix.patch affected only xml values containing an xml declaration >> with >> "encoding" attribute. In UTF8 databases, this latest proposal >> (xpath-parsing-error-

Re: [HACKERS] proposal - Default namespaces for XPath expressions (PostgreSQL 11)

2017-10-02 12:22 GMT+02:00 Kyotaro HORIGUCHI < horiguchi.kyot...@lab.ntt.co.jp>: > Hi, thanks for the new patch. > > # The patch is missing xpath_parser.h. That of the first patch was usable. > > At Thu, 28 Sep 2017 07:59:41 +0200, Pavel Stehule <pavel.steh...@gmail.com> > wrote in

Re: [HACKERS] fresh regression - regproc result contains unwanted schema

2017-10-14 17:26 GMT+02:00 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.com> writes: > > When function is overwritten, then regproc result contains schema, > although > > it is on search_path > > There's no "fresh regression"

[HACKERS] fresh regression - regproc result contains unwanted schema

it is on search_path This behave breaks regress tests (and it is not consistent) Tested on master Regards Pavel

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2017-09-19 20:49 GMT+02:00 Merlin Moncure <mmonc...@gmail.com>: > On Tue, Sep 19, 2017 at 1:37 PM, Robert Haas <robertmh...@gmail.com> > wrote: > > On Tue, Sep 19, 2017 at 12:45 PM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > >>> You ca

Re: [HACKERS] GUC for cleanup indexes threshold.

append-only tables, to freeze the Visibility Map. DP> The new status of this patch is: Ready for Committer Seems like, we may also going to hit it and it would be cool this vacuum issue solved for next PG version. -- With best wishes, Pavel mailto:pa...@gf.microola

Re: [HACKERS] is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

2017-10-08 19:10 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-10-08 19:04 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > >> >> >> 2017-10-08 18:59 GMT+02:00 Andres Freund <and...@anarazel.de>: >> >>> On 2017-10

[HACKERS] Re: is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

plt LIMIT 1; > EXCEPTION > WHEN OTHERS THEN > mADRA := NULL; > END; > > > > Result:=mADRA; > return(Result); > end; > > So this issue is really related to tupleDesc management > I found a bug in this workaround. It doesn't work > > >> Pavel >> >> >> >

Re: [HACKERS] is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

2017-10-08 19:04 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-10-08 18:59 GMT+02:00 Andres Freund <and...@anarazel.de>: > >> On 2017-10-08 18:57:28 +0200, Pavel Stehule wrote: >> > 2017-10-08 18:44 GMT+02:00 Andres Freu

Re: [HACKERS] is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

2017-10-08 18:59 GMT+02:00 Andres Freund <and...@anarazel.de>: > On 2017-10-08 18:57:28 +0200, Pavel Stehule wrote: > > 2017-10-08 18:44 GMT+02:00 Andres Freund <and...@anarazel.de>: > > > > > Hi, > > > > > > On 2017-10-08 18:36:23 +02

Re: [HACKERS] is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

2017-10-08 18:44 GMT+02:00 Andres Freund <and...@anarazel.de>: > Hi, > > On 2017-10-08 18:36:23 +0200, Pavel Stehule wrote: > > 2. Lot of used tables are pretty wide - 60, 120, .. columns > > > > Now, I am doing profiling, and I see so most time is related to &g

[HACKERS] Re: is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

2017-10-08 18:36 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > Hi > > I am looking why some queries are significantly slower on PostgreSQL than > on Oracle, although there is pretty simple plan. The queries are usually > 10x times slower on Postgres than on Oracle. >

[HACKERS] is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug?

long in this case. It should be reduced to few fields? 2. If is not possible to reduce the number of fields of target list, is possible to store tupledesc template to plan? Without this issue, the Postgres has same speed or is faster than Ora. I can send a schema by some private channel. Regards Pavel

Re: [HACKERS] [PATCH] A hook for session start

2017-10-07 6:49 GMT+02:00 Nico Williams <n...@cryptonector.com>: > On Sat, Oct 07, 2017 at 05:44:00AM +0200, Pavel Stehule wrote: > > 2017-10-06 21:36 GMT+02:00 Nico Williams <n...@cryptonector.com>: > > > But the nice thing about them is that you need only create th

Re: [HACKERS] [PATCH] A hook for session start

2017-10-06 21:36 GMT+02:00 Nico Williams <n...@cryptonector.com>: > On Fri, Oct 06, 2017 at 08:51:53PM +0200, Pavel Stehule wrote: > > 2017-10-06 20:39 GMT+02:00 Nico Williams <n...@cryptonector.com>: > > > On Fri, Oct 06, 2017 at 06:37:57PM +0200, Pavel Stehule

Re: [HACKERS] [PATCH] A hook for session start

2017-10-06 20:39 GMT+02:00 Nico Williams <n...@cryptonector.com>: > On Fri, Oct 06, 2017 at 06:37:57PM +0200, Pavel Stehule wrote: > > 2017-10-06 6:48 GMT+02:00 Nico Williams <n...@cryptonector.com>: > > > On Fri, Oct 06, 2017 at 04:52:09AM +0200, Pavel Stehule wrot

Re: [HACKERS] [PATCH] A hook for session start

2017-10-06 6:48 GMT+02:00 Nico Williams <n...@cryptonector.com>: > On Fri, Oct 06, 2017 at 04:52:09AM +0200, Pavel Stehule wrote: > > 2017-10-05 22:31 GMT+02:00 Nico Williams <n...@cryptonector.com>: > > > On Tue, Aug 01, 2017 at 03:36:23PM -0400, Peter Eisentraut w

Re: [HACKERS] [PATCH] A hook for session start

hould to support this case more :( Probably is better, so it is hard to use local TEMP tables. Regards Pavel > > Nico > -- > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers >

Re: [HACKERS] why subplan is 10x faster then function?

2017-10-01 12:45 GMT+02:00 Sokolov Yura <funny.fal...@postgrespro.ru>: > 1 октября 2017 г. 12:42:14 GMT+03:00, Pavel Stehule < > pavel.steh...@gmail.com> пишет: > >2017-09-30 23:23 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > >> Hi >

Re: [HACKERS] issue: record or row variable cannot be part of multiple-item INTO list

to scalar. List of scalars should be disallowed as target for composite value should be a) disallowed every time, b) disallowed when some target var is a composite. The differences between assign command and INTO command can be messy too. So the best solution should be one rules for := and INTO - but I am not sure if it is possible Comments? Regards Pavel > regards, tom lane >

Re: [HACKERS] proposal - Default namespaces for XPath expressions (PostgreSQL 11)

2017-10-02 12:22 GMT+02:00 Kyotaro HORIGUCHI < horiguchi.kyot...@lab.ntt.co.jp>: > Hi, thanks for the new patch. > > # The patch is missing xpath_parser.h. That of the first patch was usable. > > At Thu, 28 Sep 2017 07:59:41 +0200, Pavel Stehule <pavel.steh...@gmail.com> > wrote in

Re: [HACKERS] SQL/JSON in PostgreSQL

2017-09-30 1:06 GMT+02:00 Nikita Glukhov <n.glu...@postgrespro.ru>: > On 29.09.2017 20:07, Pavel Stehule wrote: > > 2017-09-29 12:15 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > >> >> 2017-09-29 12:09 GMT+02:00 Nikita Glukhov <n.glu...@postgrespro.ru

Re: [HACKERS] why subplan is 10x faster then function?

2017-09-30 23:23 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > Hi > > I have some strange slow queries based on usage "view" functions > > one function looks like this: > > CREATE OR REPLACE FUNCTION ides_funcs.najdatsplt_cislo_exekuce(mid_najdatsplt &

Re: [HACKERS] why subplan is 10x faster then function?

2017-10-01 12:45 GMT+02:00 Sokolov Yura <funny.fal...@postgrespro.ru>: > 1 октября 2017 г. 12:42:14 GMT+03:00, Pavel Stehule < > pavel.steh...@gmail.com> пишет: > >2017-09-30 23:23 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > >> Hi >

Re: [HACKERS] why subplan is 10x faster then function?

2017-09-30 23:23 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > Hi > > I have some strange slow queries based on usage "view" functions > > one function looks like this: > > CREATE OR REPLACE FUNCTION ides_funcs.najdatsplt_cislo_exekuce(mid_najdatsplt &

Re: [HACKERS] extension build issue with PostgreSQL 10 on Centos6

2017-10-01 4:55 GMT+02:00 Devrim Gündüz <dev...@gunduz.org>: > > Hi, > > On Sat, 2017-09-30 at 11:15 -0400, Tom Lane wrote: > > So the point is that postgresql-devel now needs to have a dependency > > on icu-devel. > > Oh, I see. Ack, added. Will appe

[HACKERS] why subplan is 10x faster then function?

result on 9.6, 10. Is known overhead of function execution? Regards Pavel

Re: [HACKERS] extension build issue with PostgreSQL 10 on Centos6

2017-09-30 8:18 GMT+02:00 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.com> writes: > > /usr/pgsql-10/include/server/utils/pg_locale.h:19:26: error: > > unicode/ucol.h: Adresář nebo soubor neexistuje > > > This mean not optional dependenc

Re: [HACKERS] extension build issue with PostgreSQL 10 on Centos6

2017-09-30 7:54 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > Hi > > There is new, not well solved dependency. I have not any problem to build > extension with PostgreSQL 9.6 there > > [oracle@ora2pg plpgsql_check]$ make > gcc -Wall -Wmissing-prototypes -Wpo

[HACKERS] extension build issue with PostgreSQL 10 on Centos6

This mean not optional dependency on ICU. Installed from rpm Regards Pavel

Re: [HACKERS] SQL/JSON in PostgreSQL

2017-09-30 1:06 GMT+02:00 Nikita Glukhov <n.glu...@postgrespro.ru>: > On 29.09.2017 20:07, Pavel Stehule wrote: > > 2017-09-29 12:15 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > >> >> 2017-09-29 12:09 GMT+02:00 Nikita Glukhov <n.glu...@postgrespro.ru

Re: [HACKERS] SQL/JSON in PostgreSQL

2017-09-29 12:15 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-09-29 12:09 GMT+02:00 Nikita Glukhov <n.glu...@postgrespro.ru>: > >> >> >> I have some free time now. Is it last version? >> >> Regards >> >> Pavel

Re: [HACKERS] SQL/JSON in PostgreSQL

2017-09-29 12:09 GMT+02:00 Nikita Glukhov <n.glu...@postgrespro.ru>: > > > I have some free time now. Is it last version? > > Regards > > Pavel > > Yes, this is still the latest version. Now I am working only on unfinished > WIP > patch no. 9, but I think

Re: [HACKERS] SQL/JSON in PostgreSQL

JSON path with > explicitly > specified types is rather interesting, and I think it should be shown now > to get a some kind of pre-review. > > We are supporting v11 and v10 branches in our github repository: > > https://github.com/postgrespro/sqljson/tree/sqljson > https://github.com/postgrespro/sqljson/tree/sqljson_wip > https://github.com/postgrespro/sqljson/tree/sqljson_v10 > https://github.com/postgrespro/sqljson/tree/sqljson_v10_wip > > Attached patches can be produced simply by combining groups of consecutive > commits from these branches. > > I have some free time now. Is it last version? Regards Pavel -- > Nikita Glukhov > Postgres Professional:http://www.postgrespro.com > The Russian Postgres Company > >

[HACKERS] plpgsql_check future

for other than Linux platforms. The builds on MS Win are difficult for me, because I don't use Windows. The plpgsql_check is too big be part of contrib. But I invite some similar, what help me with mentioned issues. Any ideas? Regards Pavel

Re: [HACKERS] proposal - Default namespaces for XPath expressions (PostgreSQL 11)

Hi now xpath and xpath_exists supports default namespace too updated doc, fixed all variants of expected result test file Regards Pavel diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 2f036015cc..610f709933 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml

Re: [HACKERS] proposal - Default namespaces for XPath expressions (PostgreSQL 11)

Hi 2017-09-25 13:25 GMT+02:00 Kyotaro HORIGUCHI < horiguchi.kyot...@lab.ntt.co.jp>: > Hello, this patch have been ignored for a long time since its proposal... > > At Sat, 11 Mar 2017 20:44:31 +0100, Pavel Stehule <pavel.steh...@gmail.com> > wrote in <CAFj8

Re: [HACKERS] logical replication and statistics

Hi I did recheck and now it looks like it is expected. Probably I did some wrong Sorry for noise Regards Pavel

Re: [HACKERS] logical replication and statistics

2017-09-26 11:56 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-09-26 11:51 GMT+02:00 Masahiko Sawada <sawada.m...@gmail.com>: > >> On Tue, Sep 26, 2017 at 2:50 AM, Pavel Stehule <pavel.steh...@gmail.com> >> wrote: >> > >>

Re: [HACKERS] logical replication and statistics

2017-09-26 11:51 GMT+02:00 Masahiko Sawada <sawada.m...@gmail.com>: > On Tue, Sep 26, 2017 at 2:50 AM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > > > > > > 2017-09-25 19:23 GMT+02:00 Petr Jelinek <petr.jeli...@2ndquadrant.com>: > >> &

Re: [HACKERS] logical replication and statistics

2017-09-25 19:23 GMT+02:00 Petr Jelinek <petr.jeli...@2ndquadrant.com>: > On 25/09/17 19:19, Tom Lane wrote: > > Pavel Stehule <pavel.steh...@gmail.com> writes: > >> I had two instances on one server with different port. I am sure, so > >> replication was f

Re: [HACKERS] logical replication and statistics

2017-09-25 18:30 GMT+02:00 Petr Jelinek <petr.jeli...@2ndquadrant.com>: > On 25/09/17 13:33, Pavel Stehule wrote: > > > > > > 2017-09-25 13:12 GMT+02:00 Masahiko Sawada <sawada.m...@gmail.com > > <mailto:sawada.m...@gmail.com>>: > > >

Re: [HACKERS] logical replication and statistics

2017-09-25 13:12 GMT+02:00 Masahiko Sawada <sawada.m...@gmail.com>: > On Mon, Sep 25, 2017 at 12:58 AM, Pavel Stehule <pavel.steh...@gmail.com> > wrote: > > Hi > > > > I did trivial example of logical replication (one table, one publication, > > one subsc

[HACKERS] logical replication and statistics

enabled? Regards Pavel

Re: [HACKERS] pgbench - use enum for meta commands

ing comparisons to check for the various meta commands is > neither efficient nor readable. Use an enum instead, which are extensively > used already for other similar purposes. > +1 Pavel > -- > Fabien. > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

2017-09-22 21:12 GMT+02:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 9/22/17 09:16, Pavel Stehule wrote: > > Example: somebody set SORT_COLUMNS to schema_name value. This is > > nonsense for \l command > > > > Now, I am thinking so more corr

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

2017-09-21 20:30 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > > 2017-09-21 20:20 GMT+02:00 Peter Eisentraut <peter.eisentraut@2ndquadrant. > com>: > >> On 9/21/17 13:54, Pavel Stehule wrote: >> > I see where you are coming from, but there

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-09-22 10:15 GMT+02:00 Peter Moser <pitiz...@gmail.com>: > 2017-09-22 10:06 GMT+02:00 Pavel Stehule <pavel.steh...@gmail.com>: > > ANSI SQL 2011 has temporal data support > > > > https://www.slideshare.net/CraigBaumunk/temporal- > extensions-tosql2011

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2011 has temporal data support https://www.slideshare.net/CraigBaumunk/temporal-extensions-tosql20112012010438 Regards Pavel Stehule

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

2017-09-21 20:20 GMT+02:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 9/21/17 13:54, Pavel Stehule wrote: > > I see where you are coming from, but there is no association in the > > existing UI that equates "+" to the word "verb

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

2017-09-21 15:30 GMT+02:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 9/21/17 04:27, Pavel Stehule wrote: > > yes. It was designed for + commands only. Can be enhanced to all > > commands - then VERBOSE prefix should be removed - not sure if it is > > ne

Re: [HACKERS] Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

2017-09-21 10:19 GMT+02:00 Alexander Korotkov <a.korot...@postgrespro.ru>: > On Thu, Sep 21, 2017 at 1:53 AM, Peter Eisentraut < > peter.eisentr...@2ndquadrant.com> wrote: > >> On 9/8/17 00:13, Pavel Stehule wrote: >> > I am sending rebased patch >>

Re: [HACKERS] type cache for concat functions

2017-09-19 21:11 GMT+02:00 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.com> writes: > > [ faster-concat-2.patch ] > > Pushed with some cosmetic adjustments (mostly better comments). > Thank you very much Pavel > regards, tom lane >

Re: [HACKERS] Re: issue: record or row variable cannot be part of multiple-item INTO list

2017-09-19 20:29 GMT+02:00 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.com> writes: > > 2017-09-14 12:33 GMT+02:00 Anthony Bykov <a.by...@postgrespro.ru>: > >> As far as I understand, this patch adds functionality (correct me if

  1   2   3   4   5   6   7   8   9   10   >