Hi
2017-11-13 13:15 GMT+01:00 Pavel Golub :
> 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
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
2017-11-11 21:19 GMT+01:00 Noah Misch :
> On Sun, Nov 05, 2017 at 06:10:04PM +0100, Pavel Stehule wrote:
> > Hi
> >
> > 2017-11-05 4:07 GMT+01:00 Noah Misch :
> >
> > > On Tue, Oct 17, 2017 at 06:06:40AM +0200, Pavel Stehule wrote:
> > > > Please
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.
>
ready 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\l
eate 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);
>
>
I am l
processed and logged in audit log too.
Regards
Pavel
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 to break original tuple
2017-11-09 21:12 GMT+01:00 Pavel Stehule :
>
>
> 2017-11-09 21:03 GMT+01:00 Fabien COELHO :
>
>>
>> Hello Pavel,
>>
>> I hope so I fixed all mentioned issues.
>>>
>>
>> Patch applies with a warning:
>>
>> > git apply ~/psq
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
2017-11-09 21:03 GMT+01:00 Fabien COELHO :
>
> 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 line at EOF.
> +
&g
Hi
2017-08-24 5:50 GMT+02:00 Fabien COELHO :
>
> 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.
>
> Missing break in switch, even if l
8 conflicts on doc/src/sgml/func.sgml
>
>
> At Sun, 15 Oct 2017 12:06:11 +0200, Pavel Stehule
> wrote in b9efon...@mail.gmail.com>
> > 2017-10-02 12:22 GMT+02:00 Kyotaro HORIGUCHI <
> > horiguchi.kyot...@lab.ntt.co.jp>:
> >
> > > Hi, thanks for the new
2017-11-08 15:31 GMT+01:00 Pavel Stehule :
>
>
> 2017-11-08 15:23 GMT+01:00 Peter Eisentraut 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 in
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
Hi
2017-11-05 4:07 GMT+01:00 Noah Misch :
> 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
> this week's
2017-11-02 13:35 GMT+01:00 Robert Haas :
> On Thu, Oct 26, 2017 at 12:51 PM, Pavel Stehule
> wrote:
> > The variables can be modified by SQL command SET (this is taken from
> > standard, and it natural)
> >
> > SET varname = expression;
>
> Overloading SET to
2017-11-02 16:07 GMT+01:00 Craig Ringer :
> On 26 October 2017 at 15:21, Pavel Stehule
> wrote:
> > Hi,
> >
> > I propose a new database object - a variable.
>
> Didn't we have a pretty long discussion about this already in
>
> Yeah.
>
> https://ww
2017-11-02 16:35 GMT+01:00 Nico Williams :
> On Thu, Nov 02, 2017 at 06:05:54PM +0530, Robert Haas wrote:
> > On Thu, Oct 26, 2017 at 12:51 PM, Pavel Stehule
> wrote:
> > > The variables can be modified by SQL command SET (this is taken from
> > > standard, a
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
>
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
>
Hi
better to send it as attachment
Regards
Pavel
2015-03-19 23:41 GMT+01:00 David Christensen :
> 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 provided. This would come in mo
d patch 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
> while 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?
s 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
>
2017-10-31 22:28 GMT+01:00 srielau :
> 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 different meaning fr
2017-10-31 22:08 GMT+01:00 Serge Rielau :
> 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 CREATE TEMP VAR is anough.
>
>
stems one
> has worked 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/
Hi
2017-10-30 22:42 GMT+01:00 srielau :
> 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 session private obje
ansaction control in 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
2017-10-28 23:35 GMT+02:00 Alexander Korotkov :
> On Sat, Oct 28, 2017 at 3:46 PM, Pavel Stehule
> wrote:
>
>> 2017-09-22 21:31 GMT+02:00 Pavel Stehule :
>>
>>>
>>>
>>> 2017-09-22 21:12 GMT+02:00 Peter Eisentraut <
>>> peter.eisentr..
Hi
2017-10-28 16:24 GMT+02:00 Chris Travers :
>
>
> On Thu, Oct 26, 2017 at 9:21 AM, Pavel Stehule
> wrote:
>
>> Hi,
>>
>> I propose a new database object - a variable. The variable is persistent
>> object, that holds unshared session based not trans
Hi
2017-09-22 21:31 GMT+02:00 Pavel Stehule :
>
>
> 2017-09-22 21:12 GMT+02:00 Peter Eisentraut 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
>>
2017-10-27 15:38 GMT+02:00 Gilles Darold :
> 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 transactional
> > in memory val
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
&
(3114) idle
32274 ?Ss 0:00 postgres: ides ides_jmmaj_akt 192.168.1.50(3124)
idle
regards
Pavel
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 persis
Hi
2017-10-27 0:07 GMT+02:00 Nico Williams :
> 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 possible, as well as pg_id
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
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.
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 building
> --
> Fabien
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
2017-10-22 9:08 GMT+02:00 Magnus Hagander :
>
>
> On Sun, Oct 22, 2017 at 9:02 AM, Pavel Stehule
> wrote:
>
>> Hi
>>
>> I sent correct mail, that requires the approval - maybe bad filter?
>>
>
> There are some pretty restrictive filters in place o
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
us 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_user() already
re
2017-10-17 1:57 GMT+02:00 Noah Misch :
> 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). Among
> > >
2017-08-21 6:25 GMT+02:00 Pavel Stehule :
>
>
>> xpath-bugfix.patch affected only xml values containing an xml declaration
>> with
>> "encoding" attribute. In UTF8 databases, this latest proposal
>> (xpath-parsing-error-fix.patch) is equivalent to xpath
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
> wrote in mail.gmail
2017-10-14 17:26 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > When function is overwritten, then regproc result contains schema,
> although
> > it is on search_path
>
> There's no "fresh regression" here, it's done that more or less
ins schema, although
it is on search_path
This behave breaks regress tests (and it is not consistent)
Tested on master
Regards
Pavel
2017-09-19 20:49 GMT+02:00 Merlin Moncure :
> On Tue, Sep 19, 2017 at 1:37 PM, Robert Haas
> wrote:
> > On Tue, Sep 19, 2017 at 12:45 PM, Pavel Stehule
> wrote:
> >>> You can already set a GUC with function scope. I'm not getting your
> >>> point.
&
in on
DP> 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
2017-10-08 19:10 GMT+02:00 Pavel Stehule :
>
>
> 2017-10-08 19:04 GMT+02:00 Pavel Stehule :
>
>>
>>
>> 2017-10-08 18:59 GMT+02:00 Andres Freund :
>>
>>> On 2017-10-08 18:57:28 +0200, Pavel Stehule wrote:
>>> > 2017-10-08 18:44 GMT+02:00 And
IMIT 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
>>
>>
>>
>
2017-10-08 19:04 GMT+02:00 Pavel Stehule :
>
>
> 2017-10-08 18:59 GMT+02:00 Andres Freund :
>
>> On 2017-10-08 18:57:28 +0200, Pavel Stehule wrote:
>> > 2017-10-08 18:44 GMT+02:00 Andres Freund :
>> >
>> > > Hi,
>> > >
>> > &g
2017-10-08 18:59 GMT+02:00 Andres Freund :
> On 2017-10-08 18:57:28 +0200, Pavel Stehule wrote:
> > 2017-10-08 18:44 GMT+02:00 Andres Freund :
> >
> > > Hi,
> > >
> > > On 2017-10-08 18:36:23 +0200, Pavel Stehule wrote:
> > > > 2. Lo
2017-10-08 18:44 GMT+02:00 Andres Freund :
> 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
> >
> > ExecTy
2017-10-08 18:36 GMT+02:00 Pavel Stehule :
> 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.
>
> I migrate old Oracle ap
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
2017-10-07 6:49 GMT+02:00 Nico Williams :
> On Sat, Oct 07, 2017 at 05:44:00AM +0200, Pavel Stehule wrote:
> > 2017-10-06 21:36 GMT+02:00 Nico Williams :
> > > But the nice thing about them is that you need only create them once,
> so
> > > leave them in the catalog
2017-10-06 21:36 GMT+02:00 Nico Williams :
> On Fri, Oct 06, 2017 at 08:51:53PM +0200, Pavel Stehule wrote:
> > 2017-10-06 20:39 GMT+02:00 Nico Williams :
> > > On Fri, Oct 06, 2017 at 06:37:57PM +0200, Pavel Stehule wrote:
> > > > When we talked about th
2017-10-06 20:39 GMT+02:00 Nico Williams :
> On Fri, Oct 06, 2017 at 06:37:57PM +0200, Pavel Stehule wrote:
> > 2017-10-06 6:48 GMT+02:00 Nico Williams :
> > > On Fri, Oct 06, 2017 at 04:52:09AM +0200, Pavel Stehule wrote:
> > > > Current TEMP tables, if you do
2017-10-06 6:48 GMT+02:00 Nico Williams :
> On Fri, Oct 06, 2017 at 04:52:09AM +0200, Pavel Stehule wrote:
> > 2017-10-05 22:31 GMT+02:00 Nico Williams :
> > > On Tue, Aug 01, 2017 at 03:36:23PM -0400, Peter Eisentraut wrote:
> > > > On 7/21/17 13:14, Jim Mlodgenski
erhead - with possible risk of performance lost (system catalog bloat).
pretty significant performance issue of my customers are related to temp
tables usage (under high load)
So often creating local temp tables is antipattern (in Postgres)
unfortunately.
I am not sure, if we should to support this case m
2017-10-01 12:45 GMT+02:00 Sokolov Yura :
> 1 октября 2017 г. 12:42:14 GMT+03:00, Pavel Stehule <
> pavel.steh...@gmail.com> пишет:
> >2017-09-30 23:23 GMT+02:00 Pavel Stehule :
> >
> >> Hi
> >>
> >> I have some strange slow queries based on
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
>
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
> wrote in mail.gmail
2017-09-30 1:06 GMT+02:00 Nikita Glukhov :
> On 29.09.2017 20:07, Pavel Stehule wrote:
>
> 2017-09-29 12:15 GMT+02:00 Pavel Stehule :
>
>>
>> 2017-09-29 12:09 GMT+02:00 Nikita Glukhov :
>>
>>>
>>>
>>> I have some free time now. Is it last
2017-09-30 23:23 GMT+02:00 Pavel Stehule :
> 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
> bigint)
> RETURNS charac
2017-10-01 12:45 GMT+02:00 Sokolov Yura :
> 1 октября 2017 г. 12:42:14 GMT+03:00, Pavel Stehule <
> pavel.steh...@gmail.com> пишет:
> >2017-09-30 23:23 GMT+02:00 Pavel Stehule :
> >
> >> Hi
> >>
> >> I have some strange slow queries based on
2017-09-30 23:23 GMT+02:00 Pavel Stehule :
> 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
> bigint)
> RETURNS charac
2017-10-01 4:55 GMT+02:00 Devrim Gündüz :
>
> 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 appear in 10.0 RPMs.
>
Thank you
ult on 9.6, 10.
Is known overhead of function execution?
Regards
Pavel
2017-09-30 8:18 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > /usr/pgsql-10/include/server/utils/pg_locale.h:19:26: error:
> > unicode/ucol.h: Adresář nebo soubor neexistuje
>
> > This mean not optional dependency on ICU.
>
> Really? That file has
>
>
2017-09-30 7:54 GMT+02:00 Pavel Stehule :
> 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 -Wpointer-arith
> -Wdeclaration
This mean not optional dependency on ICU.
Installed from rpm
Regards
Pavel
2017-09-30 1:06 GMT+02:00 Nikita Glukhov :
> On 29.09.2017 20:07, Pavel Stehule wrote:
>
> 2017-09-29 12:15 GMT+02:00 Pavel Stehule :
>
>>
>> 2017-09-29 12:09 GMT+02:00 Nikita Glukhov :
>>
>>>
>>>
>>> I have some free time now. Is it last
2017-09-29 12:15 GMT+02:00 Pavel Stehule :
>
>
> 2017-09-29 12:09 GMT+02:00 Nikita Glukhov :
>
>>
>>
>> I have some free time now. Is it last version?
>>
>> Regards
>>
>> Pavel
>>
>> Yes, this is still the latest version. Now I a
2017-09-29 12:09 GMT+02:00 Nikita Glukhov :
>
>
> 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 it should be reviewed th
g, 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
>
>
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
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
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
> wrote in com>
> > Hi
> >
> > This pr
Hi
I did recheck and now it looks like it is expected.
Probably I did some wrong
Sorry for noise
Regards
Pavel
2017-09-26 11:56 GMT+02:00 Pavel Stehule :
>
>
> 2017-09-26 11:51 GMT+02:00 Masahiko Sawada :
>
>> On Tue, Sep 26, 2017 at 2:50 AM, Pavel Stehule
>> wrote:
>> >
>> >
>> > 2017-09-25 19:23 GMT+02:00 Petr Jelinek :
>> >>
>>
2017-09-26 11:51 GMT+02:00 Masahiko Sawada :
> On Tue, Sep 26, 2017 at 2:50 AM, Pavel Stehule
> wrote:
> >
> >
> > 2017-09-25 19:23 GMT+02:00 Petr Jelinek :
> >>
> >> On 25/09/17 19:19, Tom Lane wrote:
> >> > Pavel Stehule writes:
> >&
2017-09-25 19:23 GMT+02:00 Petr Jelinek :
> On 25/09/17 19:19, Tom Lane wrote:
> > Pavel Stehule writes:
> >> I had two instances on one server with different port. I am sure, so
> >> replication was functional. Only one issue is statistics
> >
> >>
2017-09-25 18:30 GMT+02:00 Petr Jelinek :
> On 25/09/17 13:33, Pavel Stehule wrote:
> >
> >
> > 2017-09-25 13:12 GMT+02:00 Masahiko Sawada > <mailto:sawada.m...@gmail.com>>:
> >
> > On Mon, Sep 25, 2017 at 12:58 AM, Pavel Stehule
> > m
2017-09-25 13:12 GMT+02:00 Masahiko Sawada :
> On Mon, Sep 25, 2017 at 12:58 AM, Pavel Stehule
> wrote:
> > Hi
> >
> > I did trivial example of logical replication (one table, one publication,
> > one subscription)
> >
> > I am little bit surpris
enabled?
Regards
Pavel
s 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)
> To make changes to y
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 correct
2017-09-21 20:30 GMT+02:00 Pavel Stehule :
>
>
> 2017-09-21 20:20 GMT+02:00 Peter Eisentraut 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 &
2017-09-22 10:15 GMT+02:00 Peter Moser :
> 2017-09-22 10:06 GMT+02:00 Pavel Stehule :
> > ANSI SQL 2011 has temporal data support
> >
> > https://www.slideshare.net/CraigBaumunk/temporal-
> extensions-tosql20112012010438
>
> As operations it only supports temporal
ideshare.net/CraigBaumunk/temporal-extensions-tosql20112012010438
Regards
Pavel Stehule
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 "verbose&
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
2017-09-21 10:19 GMT+02:00 Alexander Korotkov :
> 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
>> >
>> > rebased again
2017-09-19 21:11 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > [ faster-concat-2.patch ]
>
> Pushed with some cosmetic adjustments (mostly better comments).
>
Thank you very much
Pavel
> regards, tom lane
>
2017-09-19 20:29 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > 2017-09-14 12:33 GMT+02:00 Anthony Bykov :
> >> As far as I understand, this patch adds functionality (correct me if I'm
> >> wrong) for users. Shouldn't there be any changes in doc/src/sgm
1 - 100 of 5265 matches
Mail list logo
