2017-04-06 3:34 GMT+02:00 Stephen Frost :
> Andres,
>
> * Andres Freund (and...@anarazel.de) wrote:
> > On 2017-04-05 21:07:59 -0400, Stephen Frost wrote:
> > > * Andres Freund (and...@anarazel.de) wrote:
> > > > I don't yet have a good idea how to deal with moving individual cells
> > > > into fi
2017-04-05 22:33 GMT+02:00 Andres Freund :
> Hi,
>
>
> I'd like some input from other committers whether we want this. I'm
> somewhat doubtful, but don't have particularly strong feelings.
>
>
> > +
> > +
> > + Block level PRAGMA
> > +
> > +
> > +PRAGMA
> > +in PL/pgSQL
> > +
>
2017-04-05 23:22 GMT+02:00 Tom Lane :
> Andres Freund writes:
> > I'd like some input from other committers whether we want this. I'm
> > somewhat doubtful, but don't have particularly strong feelings.
>
> I don't really want to expose the workings of the plancache at user level.
> The heuristic
>
> That echoes my perception - so let's move this to the next CF? It's not
> like this patch has been pending for very long.
>
sure
Regards
Pavel
>
> - Andres
>
2017-04-06 8:08 GMT+02:00 Pavel Stehule :
>
>
> 2017-04-05 23:22 GMT+02:00 Tom Lane :
>
>> Andres Freund writes:
>> > I'd like some input from other committers whether we want this. I'm
>> > somewhat doubtful, but don't have particularly stron
2017-04-06 14:47 GMT+02:00 Stephen Frost :
> Greetings,
>
> * Pavel Stehule (pavel.steh...@gmail.com) wrote:
> > 2017-04-06 3:34 GMT+02:00 Stephen Frost :
> > > Having the template not require the row/column place-holders included
> > > strikes me as more li
2017-04-06 12:30 GMT+02:00 Andrew Dunstan :
>
>
> On 04/05/2017 05:41 PM, Andres Freund wrote:
> > On 2017-04-05 17:22:34 -0400, Tom Lane wrote:
> >> Andres Freund writes:
> >>> I'd like some input from other committers whether we want this. I'm
> >>> somewhat doubtful, but don't have particular
2017-04-07 9:52 GMT+02:00 Fabien COELHO :
>
> Hello Corey,
>
> \if defined varname
\if sql boolean expression to send to server
\if compare value operator value
>>>
>>> I'm still thinking:-)
>>>
>>> Independently of the my aethetical complaint against having
2017-04-07 21:04 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> I wish I could have an explanation about why the :?varname (or some other
>>> variant) syntax I suggested has a "namespace" issue.
>>>
>>> The advantage that I see is that although it is obviously ugly, it is
>>> ugly
>>> in the conti
2017-04-08 2:30 GMT+02:00 Peter Eisentraut :
> On 4/6/17 14:32, Pavel Stehule wrote:
> > I like to see any proposals about syntax or implementation.
> >
> > Using PRAGMA is one variant - introduced by PLpgSQL origin - Ada
> > language. The PRAGMA syntax can be used for
2017-04-08 12:25 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
> n
>
>> you proposal disallow client side expressions.
>>
>
> I do agree that some client side expressions are necessary. I do not want
> to disallow them.
>
> I agree so is not possible to mix server side and client side expressions.
>>
2017-04-10 13:07 GMT+02:00 Greg Stark :
> On 2 April 2017 at 07:53, Fabien COELHO wrote:
> > Note that this is already available indirectly, as show in the
> > documentation.
> >
> > SELECT some-boolean-expression AS okay \gset
> > \if :okay
> > \echo boolean expression was true
> > \el
2017-04-11 8:17 GMT+02:00 Fabien COELHO :
>
> Hello Greg,
>
> SELECT some-boolean-expression AS okay \gset
>>> \if :okay
>>>
>>
>> Am I the only one who thinks that even if \if got the ability to
>> evaluate arbitrary SQL queries I would probably still always write
>> things as above?
>>
>
> I
>
> \else
> \if :somevar > 1 and SERVER_NUM >= 10
>
should be
\if :somevar > 1 and :SERVER_NUM >= 10
> ...
> \end
>
>
2017-04-11 8:56 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> I think so some local expression evaluation could be - but it should not be
>> placed in \if statement
>>
>
> Why?
>
> \expr issupported :VERSION_NUM >= 1
>>
>
> Hmmm. Although I do not buy this, it could work as a replacement for
2017-04-11 9:07 GMT+02:00 Fabien COELHO :
>
> I think so implementation of simple expression evaluation should not be
>> hard
>>
>
> Indeed it is not hard, it is rather a matter of deciding what it should
> do, and the syntax to do it.
>
> - really just - we can expect so any variable will be repl
2017-04-12 17:05 GMT+02:00 Robert Haas :
> On Sun, Apr 2, 2017 at 3:56 PM, Tom Lane wrote:
> > So my view of this is that "send the expression to the server" ought
> > to be just one option for \if, not the only way to do it.
>
> I heartily agree. There should be some kind of client-side express
2017-04-13 17:19 GMT+02:00 Alvaro Herrera :
> Pavel Stehule wrote:
> > Hi
> >
> > When I tested XMLTABLE function I found a bug of XPATH function -
> > xpath_internal
> >
> > There xmltype is not correctly encoded to xmlChar due possible invalid
> >
>
> > I suggest to reuse pgbench expression engine, developed by Haas Robert:-)
>
> Not a bad idea (though I'm sure there are other reasonable options, too).
>
I checked the pgbench code - and I think it can work well - just add
logical operators and compare operators.
Don't need to create more c
2017-04-13 19:46 GMT+02:00 Corey Huinker :
>
>> > I suggest to reuse pgbench expression engine, developed by Haas
>> Robert:-)
>>
>> Not a bad idea (though I'm sure there are other reasonable options, too).
>>
>>
> I don't want to stand in the way of any progress in getting expressions
> into \if
2017-04-12 1:42 GMT+02:00 Fabien COELHO :
>
> Hmmm. Although I do not buy this, it could work as a replacement for \set
>>> which it seems cannot be upgraded because some people may rely on it to
>>> just store whatever comes after it in a variable.
>>>
>>
>> I have no strong opinion on how expres
2017-04-17 1:00 GMT+02:00 Fabien COELHO :
>
> I checked the pgbench expr related code.
>>
>
> 2. move pgbench expressions to separate module
>>
>
> Probably already existing "fe_utils".
>
> 3. teach pgbench expressions booleans
>>
>
> See https://commitfest.postgresql.org/14/985/
so some work is
>
>
> 4. because pgbench doesn't do early variable evaluation, implementation of
>> "defined" function is easy - we can introduce some new syntax for
>> implementation some bash patterns like "default value" or "own undefined
>> message"
>>
>
> Maybe. ISTM that a :* syntax should be thought for so
2017-04-17 10:58 GMT+02:00 Fabien COELHO :
>
> I don't think so :?xxx is good idea, because for me :xxx is related to
>> content, not to metadata
>>
>
> Hmmm. Indeed it is not. I do not see it as an issue, but it is a good
> point.
>
> Consider perl "defined $x" or "exists $f{k}". $x/$f{k} should
2017-06-18 0:50 GMT+02:00 Dmitry Dolgov <9erthali...@gmail.com>:
> > On 20 May 2017 at 10:03, Pavel Stehule wrote:
> >
> > Now concat is 2x times slower than || operator. With cached FmgrInfo for
> > output function it will be only 5%.
>
> Looks nice and doe
2017-06-17 7:58 GMT+02:00 Fabien COELHO :
>
> I have not any other comments. The implementation is trivial. I rerun all
>> tests and tests passed.
>>
>> I'll mark this patch as ready for commiters.
>>
>
> Oops, I just noticed a stupid confusion on my part which got through, I
> was setting "ERROR"
2017-06-16 8:45 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> new update - rebase, changed message
>>
>
> I did yet another rebase of your patch after Tom alphabetically ordered
> backslash commands. Here is the result.
It looks well
Thank you
Pavel
>
>
> --
> Fabien.
2017-06-19 20:24 GMT+02:00 Daniel Gustafsson :
> When terminating, or cancelling, a backend it’s currently not possible to
> let
> the signalled session know *why* it was dropped. This has nagged me in the
> past and now it happened to come up again, so I took a stab at this. The
> attached patc
Hi
2017-06-19 5:55 GMT+02:00 Pavel Stehule :
>
>
> 2017-06-17 7:58 GMT+02:00 Fabien COELHO :
>
>>
>> I have not any other comments. The implementation is trivial. I rerun all
>>> tests and tests passed.
>>>
>>> I'll mark this patch as read
2017-06-27 17:30 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> We can introduce macro SetVariableBool(vars, varname, bool) instead
>>>
>>> SetVariable(pset.vars, "ERROR", "FALSE");
>>>
>>
>> I checked source code, and it requires little bit more harder refactoring
>> because now we have SetVaria
2017-06-28 9:25 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> I agree that the existing "SetVariableBool" function is a misnommer, it
>>> should be "SetVariableOn" given what it does, and it is not what we need.
>>>
>>
>> switching default setting from ON to TRUE requires wider discussion -
>>
>
2017-06-28 10:04 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> + if (success)
>> + {
>> + char *ntuples = PQcmdTuples(results);
>> + SetVariable(pset.vars, "ROW_COUNT", *ntuples ? ntuples : "0");
>> + SetVariable(pset.vars, "ERROR", "FALSE");
>> + }
>> + else
>> + {
>> + SetVariable(pset.vars,
2017-06-30 14:23 GMT+02:00 Alex K :
> Greetings pgsql-hackers,
>
> I am a GSOC student this year, my initial proposal has been discussed
> in the following thread
> https://www.postgresql.org/message-id/flat/7179F2FD-49CE-
> 4093-AE14-1B26C5DFB0DA%40gmail.com
>
> Patch with COPY FROM errors handli
2017-06-30 15:42 GMT+02:00 Alex K :
> On Fri, Jun 30, 2017 at 3:35 PM, Pavel Stehule
> wrote:
> >
> >
> > 2017-06-30 14:23 GMT+02:00 Alex K :
> >>
> >> Thus, it results in a ~60% performance boost per each x2 multiplication
> of
> >> pa
2017-06-30 15:45 GMT+02:00 Pavel Stehule :
>
>
> 2017-06-30 15:42 GMT+02:00 Alex K :
>
>> On Fri, Jun 30, 2017 at 3:35 PM, Pavel Stehule
>> wrote:
>> >
>> >
>> > 2017-06-30 14:23 GMT+02:00 Alex K :
>> >>
>> >> Th
Hi
I wrote a special pager for psql. Surely, this pager is not good for paging
of man pages. So is not good to set it as global pager. We can introduce
new env variable PSQL_PAGER for this purpose. It can work similar like
PSQL_EDITOR variable.
Notes, comments?
Regards
Pavel
2017-07-26 15:27 GMT+02:00 Robert Haas :
> On Wed, Jun 21, 2017 at 10:01 AM, Remi Colinet
> wrote:
> > test=# SELECT pid, ppid, bid, concat(repeat(' ', 3 * indent),name),
> value,
> > unit FROM pg_progress(0,0);
> > pid | ppid | bid | concat | value | unit
> > ---+--
Hi
attached trivial patch for missing tab complete for \pset pager setting
Regards
Pavel
diff --git a/src/bin/psql/tab-complete.c b/src/bin/psql/tab-complete.c
index e9fdc908c7..1b15c5b0d1 100644
--- a/src/bin/psql/tab-complete.c
+++ b/src/bin/psql/tab-complete.c
@@ -3536,6 +3536,8 @@ psql_compl
Hi
2017-07-26 13:15 GMT+02:00 Dagfinn Ilmari Mannsåker :
> Pavel Stehule writes:
>
> > Hi
> >
> > I wrote a special pager for psql. Surely, this pager is not good for
> paging
> > of man pages. So is not good to set it as global pager. We can introduce
> &g
2017-07-31 11:09 GMT+02:00 Remi Colinet :
>
>
> 2017-07-26 15:27 GMT+02:00 Robert Haas :
>
>> On Wed, Jun 21, 2017 at 10:01 AM, Remi Colinet
>> wrote:
>> > test=# SELECT pid, ppid, bid, concat(repeat(' ', 3 * indent),name),
>> value,
>> > unit FROM pg_progress(0,0);
>> > pid | ppid | bid |
ot;: 34, +
> "blocks fetched": 18436,+
> "blocks total": 83334, +
> "blocks percent": 22,
2017-08-03 22:14 GMT+02:00 Peter Eisentraut <
peter.eisentr...@2ndquadrant.com>:
> I'm looking to update the SQL conformance list for the release. I'm
> wondering whether the new xmltable feature fully completes the following
> items:
>
> X300XMLTable
> X301XMLTable: derived column list o
2017-08-03 22:54 GMT+02:00 Pavel Stehule :
>
>
> 2017-08-03 22:14 GMT+02:00 Peter Eisentraut com>:
>
>> I'm looking to update the SQL conformance list for the release. I'm
>> wondering whether the new xmltable feature fully completes the following
>
2017-08-07 20:36 GMT+02:00 Peter Eisentraut <
peter.eisentr...@2ndquadrant.com>:
> On 8/3/17 17:07, Pavel Stehule wrote:
> > I'm looking to update the SQL conformance list for the release.
> I'm
> > wondering whether the new xm
Hi
2017-08-13 20:33 GMT+02:00 Fabien COELHO :
>
> Here is a v11.
>
> It is basically a simple rebase after Tom committed the "pgbench -M order"
> patch. It interfered because the compound command management also needs
> to delay part of the SQL command initialization. Some patch are luckier
> tha
Hi
2017-08-16 6:58 GMT+02:00 Thomas Munro :
> On Thu, Jul 27, 2017 at 4:19 AM, Pavel Stehule
> wrote:
> > here is a patch - it is trivial
>
> The feature makes sense, follows an existing example (PSQL_EDITOR),
> and works nicely.
>
>is platform-dependen
2017-08-16 12:47 GMT+02:00 Thomas Munro :
> On Wed, Aug 16, 2017 at 9:56 PM, Pavel Stehule
> wrote:
> > 2017-08-16 6:58 GMT+02:00 Thomas Munro :
> >> Stray blank line.
> >
> > I am not sure if I see last issue well.
>
> I meant this:
>
>
>
Hi
2017-08-15 4:37 GMT+02:00 Peter Eisentraut :
> On 3/11/17 07:06, Pavel Stehule wrote:
> > I am sending a updated version with separated sort direction in special
> > variable
>
> This patch also needs a rebase.
>
I am sending rebased patch
Regards
Pavel
&
2017-08-17 9:23 GMT+02:00 Vesa-Matti J Kari :
>
> Hello,
>
> Bash has HISTIGNORE feature that allows you to exclude certain commands
> from the command history (e.g. shutdown, reboot, rm *).
>
> Would it make any sense to add such a feature to psql (e.g. to ignore
> DROP, DELETE commands)?
>
It i
Hi
2017-08-08 2:10 GMT+02:00 Noah Misch :
> On Wed, Apr 05, 2017 at 10:53:39PM +0200, Pavel Stehule wrote:
> > 2017-03-17 4:23 GMT+01:00 Noah Misch :
> > > On Sun, Mar 12, 2017 at 10:26:33PM +0100, Pavel Stehule wrote:
> > > > 2017-03-12 21:57 GMT+01:00 Noah Mi
>
> Isn't the most correct solution to call xml_parse function?
>
I am reply to self. Probably not.
Now, I am thinking so I found a reason of this issue. The document
processed in xpath_internal is passed to libXML2 by
doc = xmlCtxtReadMemory(ctxt, (char *) string, len, NULL, NULL, 0);
We d
Hi
I am sending some POC - it does support XPATH and XMLTABLE for not UTF8
server encoding.
In this case, all strings should be converted to UTF8 before call libXML2
functions, and result should be converted back from UTF8.
I found some previous experiments https://marc.info/?l=pgsql-bug
s&m=12
Hi
2017-08-19 22:53 GMT+02:00 Pavel Stehule :
> Hi
>
> I am sending some POC - it does support XPATH and XMLTABLE for not UTF8
> server encoding.
>
> In this case, all strings should be converted to UTF8 before call libXML2
> functions, and result should be converted back f
2017-08-20 4:17 GMT+02:00 Noah Misch :
> On Fri, Aug 18, 2017 at 11:43:19PM +0200, Pavel Stehule wrote:
> > yes, probably libXML2 try to do check from utf8 encoding to header
> > specified encoding.
>
> Yes. That has been the topic of this thread.
>
> > a) all valu
2017-08-20 9:21 GMT+02:00 Noah Misch :
> On Sun, Aug 20, 2017 at 08:46:03AM +0200, Pavel Stehule wrote:
> > 2017-08-20 4:17 GMT+02:00 Noah Misch :
> > > On Sat, Aug 19, 2017 at 10:53:19PM +0200, Pavel Stehule wrote:
> > > > I am sending some POC - it does supp
Hi
> 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-bugfix.patch. In
> non-UTF8 databases, xpath-parsing-error-fix.patch affects all xml val
>
> 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-bugfix.patch. In
> non-UTF8 databases, xpath-parsing-error-fix.patch affects all xml values
2017-04-22 11:30 GMT+02:00 Simon Riggs :
> On 21 April 2017 at 01:21, Tomas Vondra
> wrote:
> > On 04/21/2017 12:13 AM, Tom Lane wrote:
> >>
> >> Alvaro Herrera writes:
> >>>
> >>> Simon just pointed out that having the WITH clause appear in the middle
> >>> of the CREATE STATISTICS command look
2017-04-26 12:30 GMT+02:00 Konstantin Knizhnik :
>
>
> On 26.04.2017 10:49, Konstantin Knizhnik wrote:
>
>
>
> On 26.04.2017 04:00, Tsunakawa, Takayuki wrote: Are you considering some
> upper limit on the number of prepared statements?
> In this case we need some kind of LRU for maintaining cach
Hi
Sometimes I have to solve the result types of some query. It is invisible
in psql. You have to materialize table or you have to create view. Now,
when we can enhance \g command, we can introduce query describing
some like
select a, b from foo
\gdesc
| type | length | collation | .
2017-04-30 6:28 GMT+02:00 Tom Lane :
> Craig Ringer writes:
> > - as you noted, it is hard to decide when it's worth inlining vs
> > materializing for CTE terms referenced more than once.
>
> [ raised eyebrow... ] Please explain why the answer isn't trivially
> "never".
>
> There's already a pre
2017-05-01 1:21 GMT+02:00 Andres Freund :
> On 2017-04-30 07:19:21 +0200, Pavel Stehule wrote:
> > why we cannot to introduce GUC option - enable_cteoptfence ?
>
> Doesn't really solve the issue, and we've generally shied away from GUCs
> that influence behaviour
2017-04-28 6:08 GMT+02:00 Pavel Stehule :
> Hi
>
> Sometimes I have to solve the result types of some query. It is invisible
> in psql. You have to materialize table or you have to create view. Now,
> when we can enhance \g command, we can introduce query describing
>
> some
2017-05-03 18:54 GMT+02:00 David Fetter :
> On Wed, May 03, 2017 at 01:27:38PM -0300, Claudio Freire wrote:
> > On Wed, May 3, 2017 at 11:31 AM, David Fetter wrote:
> > > Are you aware of such an ORM which both supports WITH and doesn't
> > > also closely track PostgreSQL development? I'm not.
>
2017-05-03 19:33 GMT+02:00 Alvaro Herrera :
> David Fetter wrote:
>
> > When we add a "temporary" GUC, we're taking on a gigantic burden.
> > Either we support it forever somehow, or we put it on a deprecation
> > schedule immediately and expect to be answering questions about it for
> > years aft
Hi
2017-05-08 9:08 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> A complement to my previous comments:
>
> Also, maybe it would be better if the statement is cleaned up server side
>> at the end of the execution. Not sure how to achieve that, though, libpq
>> seems to lack the relevant function:
2017-05-08 12:59 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> After giving it some thoughts, I see three possible solutions:
>>>
>>> 0. Do nothing about it.
>>>I would prefer the prepare is cleaned up.
>>>
>>> 1. assign a special name, eg "_psql_gdesc_", so that
>>>DEALLOCATE "_psql_gdes
Hi
2017-05-07 22:55 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> Sometimes I have to solve the result types of some query. It is invisible
>>> in psql.
>>>
>>
> Indeed. My 0.02€ about this patch:
>
>
> About the feature:
>
> It looks useful to allow to show the resulting types of a query.
>
>
>
Hi
This is topic, that I try to solve some longer time. I would to open
discussion before summer commitfest.
The work with binary data or long text fields (multilines) or long not only
utf8 encoded XML is not well supported by psql console. Is not hard to use
binary protocol and write custom appl
2017-05-09 18:15 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> Patch applies cleanly and compiles.
>>>
>>
> Idem for v2. "make check" ok. Tests look good.
>
> I would suggest some rewording, maybe:
>>>
>>> "Show the description of the result of the current query buffer without
>>> actually execut
2017-05-09 20:37 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> [...] it is little bit worse. I cannot to distinguish between SELECT\gdesc
>> and TRUNCATE xxx\gdesc . All are valid commands and produce empty result,
>> so result of \gdesc command should be empty result too.
>>
>> postgres=# trunca
2017-05-09 21:23 GMT+02:00 Peter Eisentraut <
peter.eisentr...@2ndquadrant.com>:
> On 5/3/17 02:56, Pavel Stehule wrote:
> > Sometimes I have to solve the result types of some query. It is
> > invisible in psql. You have to materialize table or you have to
> >
Hi
2017-05-10 18:40 GMT+02:00 Remi Colinet :
> Hello,
>
> This is version 2 of the new command name PROGRESS which I wrote in order
> to monitor long running SQL queries in a Postgres backend process.
>
This patch introduce lot of reserved keyword. Why? It can breaks lot of
applications. Cannot
2017-05-09 23:00 GMT+02:00 Daniel Verite :
> Pavel Stehule wrote:
>
> > 1. using psql variables - we just need to write commands \setfrom
> > \setfrombf - this should be very simple implementation. The value can be
> > used more times. On second hand - the loaded
2017-05-11 17:16 GMT+02:00 Daniel Verite :
> Pavel Stehule wrote:
>
> > It is similar to my first or second proposal - rejected by Tom :(
>
> Doesn't it differ? ISTM that in the patches/discussion related to:
> https://commitfest.postgresql.org/11/787/
> it w
Hi
Now, I when I working on plpgsql_check, I have to check function
parameters. I can use fn_vargargnos and out_param_varno for list of
arguments and related varno(s). when I detect some issue, I am using
refname. It is not too nice now, because these refnames are $ based. Long
names are alias onl
Hi
I am working on migration large Oracle application to Postgres. When I
started migration procedures with OUT parameters I found following limit
"record or row variable cannot be part of multiple-item INTO list"
I checked code and it looks so this limit is not necessary for ROW types
(what is
2017-05-13 22:20 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > I am working on migration large Oracle application to Postgres. When I
> > started migration procedures with OUT parameters I found following limit
>
> > "record or row variable cannot be part of mult
2017-05-14 5:04 GMT+02:00 Pavel Stehule :
>
>
> 2017-05-13 22:20 GMT+02:00 Tom Lane :
>
>> Pavel Stehule writes:
>> > I am working on migration large Oracle application to Postgres. When I
>> > started migration procedures with OUT parameters I found fo
2017-05-13 18:26 GMT+02:00 Pavel Stehule :
> Hi
>
> Now, I when I working on plpgsql_check, I have to check function
> parameters. I can use fn_vargargnos and out_param_varno for list of
> arguments and related varno(s). when I detect some issue, I am using
> refname. It i
2017-05-09 23:00 GMT+02:00 Fabien COELHO :
>
> What about detecting the empty result (eg PQntuples()==0?) and writing
>>> "Empty result" instead of the strange looking empty table above? That
>>> would
>>> just mean skipping the PrintQueryResult call in this case?
>>>
>>
>> PQntuples == 0 every ti
Ahoj
viz http://blog.cleverelephant.ca/2017/05/great-postgresql.html
Pavel
2017-05-19 3:14 GMT+02:00 Peter Eisentraut :
> On 5/15/17 14:34, Pavel Stehule wrote:
> > Now, I when I working on plpgsql_check, I have to check function
> > parameters. I can use fn_vargargnos and out_param_varno for list of
> > arguments and related varno(s
2017-05-19 5:48 GMT+02:00 Pavel Stehule :
>
>
> 2017-05-19 3:14 GMT+02:00 Peter Eisentraut com>:
>
>> On 5/15/17 14:34, Pavel Stehule wrote:
>> > Now, I when I working on plpgsql_check, I have to check function
>> > parameters. I can use fn_var
Hi
Now concat is 2x times slower than || operator. With cached FmgrInfo for
output function it will be only 5%.
Regards
Pavel
diff --git a/src/backend/utils/adt/varlena.c b/src/backend/utils/adt/varlena.c
index be399f4..d3f04f8 100644
--- a/src/backend/utils/adt/varlena.c
+++ b/src/backend/utils
Hi
2017-05-20 9:15 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> I am sending a variant with message instead empty result.
>>
>
> Thanks. Patch looks good, applies, make check ok, code is neat.
>
> Personally I prefer empty result instead message.
>>
>
> Hmm. I think that this version is less li
2017-05-20 22:26 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> - Maybe tests could also exercise unnamed columns, eg:
>>> SELECT 1, 2, 3 \gdesc \g
>>>
>>
>> done
>>
>
> Can't see it. No big deal, but if you put it it did not get through, and
> there is a warning with git apply on the very la
Hi
2017-04-02 21:57 GMT+02:00 Fabien COELHO :
>
> More to the point, we already have that. See c.h:
>>
>> #define CppAsString(identifier) #identifier
>> #define CppAsString2(x) CppAsString(x)
>>
>
> Thanks for the pointer. I grepped for them without success. Here is a v4.
I am
2017-05-21 8:39 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> v6 patch applies cleanly; make check ok; code, comments, doc & tests ok;
> various interactive tests I did ok.
>
> Thanks for this useful little feature!
>
> Let's see what committers think about it.
Thank you
Pavel
>
>
> --
> Fabi
Hi
2017-04-04 23:01 GMT+02:00 Pavel Stehule :
>
>
> 2017-04-04 22:05 GMT+02:00 Fabien COELHO :
>
>>
>> After some discussions about what could be useful since psql scripts now
>> accepts tests, this patch sets a few variables which can be used by psql
>> after
2017-05-22 9:40 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> After some discussions about what could be useful since psql scripts now
accepts tests, this patch sets a few variables which can be used by psql
after a "front door" (i.e. actually typed by the user) query:
- RESU
2017-05-22 21:33 GMT+02:00 Fabien COELHO :
>
> Please find attached a v2 which hopefully takes into account all your
>>> points above.
>>>
>>> Open question: should it gather more PQerrorResultField, or the two
>>> selected one are enough? If more, which should be included?
>>>
>>
>>
>> I don't th
Hi
I am watching this patch - it looks so there are not problems. I found only
issue in documentation - new CASE expression is not documented.
Regards
Pavel
2017-05-30 7:19 GMT+02:00 Fabien COELHO :
>
> [doc about CASE...]
>>>
>>
>> I've improved it in attached v11:
>> - add a link to the CASE full documentation
>> - add an example expression with CASE ...
>>
>
> Do you think I should improve the doc further?
I am sorry, I didn't look there yet
The
Hi
Some modern or old languages (GO, Lua, CLU) has similarly designed function
OUT parameters like PLpgSQL.
In these languages is usually supported parallel assignment. It is not
supported by PLpgSQL - there is workaround - using SELECT FROM, but it is
workaround. The implementation of PA is triv
2017-06-02 10:06 GMT+02:00 Craig Ringer :
> On 2 June 2017 at 15:51, Pavel Stehule wrote:
>
> > a, b := fx();
> >
> > Comments, notes, ideas?
>
> I'd be pretty happy to have
>
> (a, b) = (x, y);
> (a, b) = f(x);
>
> which is SQL-esque.
>
2017-06-02 10:15 GMT+02:00 Pavel Stehule :
>
>
> 2017-06-02 10:06 GMT+02:00 Craig Ringer :
>
>> On 2 June 2017 at 15:51, Pavel Stehule wrote:
>>
>> > a, b := fx();
>> >
>> > Comments, notes, ideas?
>>
>> I'd be pretty happy
2017-06-02 19:05 GMT+02:00 Pavel Stehule :
>
>
> 2017-06-02 10:15 GMT+02:00 Pavel Stehule :
>
>>
>>
>> 2017-06-02 10:06 GMT+02:00 Craig Ringer :
>>
>>> On 2 June 2017 at 15:51, Pavel Stehule wrote:
>>>
>>> > a, b := fx();
>&
Hi
2017-06-04 10:47 GMT+02:00 Fabien COELHO :
>
> Hello Brent,
>
> Regarding the error message earlier
>>
>
> 'No columns or command has no result',
>>
>
> it might be clearer with the slightly longer
>>
>
> 'The result has no columns or the command has no result'.
>>
>
> I agree that a better ph
Hi
I got strange error message - false message - max connection is less on
slave than on master, although these numbers was same. The issue was in
wrong connection string in recovery conf and slave cannot to check master
and used some defaults.
Regards
Pavel
601 - 700 of 5142 matches
Mail list logo
