#x27;t*
> do "\timing interval" as that confuses the on/off state with the
> formatting selection. Maybe a \pset option?
>
>
\pset is good idea
> Also, might I suggest that leading zeroes in such a format are not
> helpful? That is, I'd want to see "
2016-07-09 11:19 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> Why you are introducing \into and not \gset like psql does?
>>
>
> Good question.
>
> The \into syntax I implemented is more generic, you can send a bunch of
> queries together and extract the results
a set of test scripts, especially to trigger various error
> cases.
>
>
Why you are introducing \into and not \gset like psql does?
Regards
Pavel
> --
> Fabien.
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
>
ogether.
>
prosrc has still benefit for me (for C hacking). Can we show data there
only for internal or C functions? I agree, it useless for PLpgSQL.
Pavel
>
> regards, tom lane
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
anded display mode, and it may not matter adding more
> information.
> Thoughts about adding this piece of information?
>
It has 11 columns. I don't see any problem to show few columns more. It is
better than missing important information.
Regards
Pavel
--
> Michael
>
>
&
2016-07-08 0:13 GMT+02:00 Peter Geoghegan :
> On Thu, Jul 7, 2016 at 2:52 PM, Corey Huinker
> wrote:
> > Wouldn't it be great if we had a way of printing timing in more human
> > friendly formats?
>
> Yes, it would. I've thought about doing this myself. So, +1 t
2016-07-07 21:57 GMT+02:00 Robert Haas :
> On Wed, Jun 1, 2016 at 7:29 AM, Pavel Stehule
> wrote:
> > Hi
> >
> > When I tested some queries, I found strange plan
> >
> > postgres=# explain analyze select s.nazev, o.nazev, o.pocet_obyvatel from
>
2016-07-06 5:17 GMT+02:00 Peter Eisentraut :
> On 7/2/16 12:40 AM, Pavel Stehule wrote:
>
>> So ANSI SQL conform implementation of JSON support is still possible in
>> Postgres.
>>
>
> It is possible, but in this case I think it's not worth it. Our built-in
&
2016-07-05 2:39 GMT+02:00 Andreas 'ads' Scherbaum :
> On 04.07.2016 18:37, Pavel Stehule wrote:
>
>>
>> I don't know if the name "strict" is best, but the name "validate" is
>> not good too. Current to_date does some validations too.
&
2016-07-05 4:33 GMT+02:00 David G. Johnston :
> On Mon, Jul 4, 2016 at 8:39 PM, Andreas 'ads' Scherbaum <
> adsm...@wars-nicht.de> wrote:
>
>> On 04.07.2016 18:37, Pavel Stehule wrote:
>>
>>>
>>> I don't know if the name "stri
ve with current state.
Now, to_date function should not be used - functions make_date,
make_timestamp are faster and safe.
postgres=# select make_date(2017,01,40);
ERROR: date field value out of range: 2017-01-40
Regards
Pavel
> If there is any legitimate use for the cur
2016-07-04 18:24 GMT+02:00 Andreas 'ads' Scherbaum :
> On 04.07.2016 05:51, Pavel Stehule wrote:
>
>>
>>
>> 2016-07-04 5:19 GMT+02:00 Pavel Stehule > <mailto:pavel.steh...@gmail.com>>:
>>
>>
>>
>> 2016-07-04 4:25 GMT+02:00
2016-07-04 5:19 GMT+02:00 Pavel Stehule :
>
>
> 2016-07-04 4:25 GMT+02:00 Craig Ringer :
>
>> On 3 July 2016 at 09:32, Euler Taveira wrote:
>>
>>> On 02-07-2016 22:04, Andreas 'ads' Scherbaum wrote:
>>> > The attached patch adds a new functi
x27;s likely faster to use a separate function too.
>
personally I prefer first variant - this is same function with stronger
check.
The name to_date_valid sounds little bit strange - maybe to_date_strict
should be better.
Regards
Pavel
>
> --
> Craig Ringer http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
use our
first argument is a array, what is not possible in standard. So ANSI SQL
conform implementation of JSON support is still possible in Postgres.
Regards
Pavel
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote D
-Opening-Plenary.pdf
>
>
Can be nice if we can write API with respects ANSI SQL. The main problem is
query language - we doesn't support JSONPath. But if we have a own regular
expression library, probably we can have i own implementation of JSONPath
Pavel
>
> --
> Sent via p
REINDEX
CONCURRENTLY is not possible call from SPI.
Can be nice to have this function in core.
Regards
Pavel
s in core, but these queries is working for
PostgreSQL 8.2 to today, so they are relatively stable.
Regards
Pavel
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
> 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
>
2016-06-13 18:52 GMT+02:00 Robert Haas :
> On Mon, Jun 13, 2016 at 3:23 AM, Pavel Stehule
> wrote:
> > There are lot of useful queries (views), that are on our wiki. Some
> queries
> > are necessary for maintenance, and I am thinking these queries should be
> >
, comments?
Regards
Pavel
opose to fix that with the attached patch.
>
>
good idea
+1
Pavel
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
2016-06-08 8:26 GMT+02:00 Kyotaro HORIGUCHI :
> At Tue, 7 Jun 2016 12:18:31 +0200, Magnus Hagander
> wrote in <
> cabuevez5qrmq4ebysbz+ujfg_3_ap361zqtgbh_ef+2j6p0...@mail.gmail.com>
> > On Tue, Jun 7, 2016 at 11:31 AM, Pavel Stehule
> > wrote:
> > >>
2016-06-07 12:18 GMT+02:00 Magnus Hagander :
>
>
> On Tue, Jun 7, 2016 at 11:31 AM, Pavel Stehule
> wrote:
>
>>
>>
>> 2016-06-07 11:29 GMT+02:00 Magnus Hagander :
>>
>>>
>>>
>>> On Tue, Jun 7, 2016 at 11:24 AM, Pavel Stehule
&g
2016-06-07 11:29 GMT+02:00 Magnus Hagander :
>
>
> On Tue, Jun 7, 2016 at 11:24 AM, Pavel Stehule
> wrote:
>
>> Hi
>>
>> I am testing speed of connection to Postgres.
>>
>> The ssl connection is slower, and it is expected. But when I configure
>
Hi
I am testing speed of connection to Postgres.
The ssl connection is slower, and it is expected. But when I configure
pg_hba.conf to disable ssl via hostnossl, then ssl is not used, but the
speed is similar to ssl.
Is it expected behave?
Regards
Pavel
*This syntax is deprecated.
>>* --
>>*/
>> static int
>> *** exec_stmt_execsql(PLpgSQL_execstate *est
>> *** 3647,3658
>> }
>> else
>> {
>> ! /* If the statement retu
l an operator. What we need is a form of
> *addressing*. If you could directly access items in a JSON doc with []
> notation then a lot of the current functions could go away, *especially* if
> the [] notation allowed things like a slice and a list of values (ie:
> json['foo',
like:
> matrix + matrix -> matrix
> matrix - scalar -> matrix
> matrix * matrix -> matrix
> transform(matrix) -> matrix
> :
>
> How about people's thought?
>
It is far to data processing - so it should be placed in PGXN.
Regards
Pavel
vity/postgresdac/) has
TPSQLDump and TPSQLRestore classes.
Details:
http://microolap.com/products/connectivity/postgresdac/help/tpsqldump_tpsqldump.htm
Also we've implemented PaGoDump and PaGoRestore utilities compatible
with native pg_dump/pg_restore: http://microolap.com/products/database/pagodu
'%', txt;
> end$$ language plpgsql;
>
> NOTICE:*===> return value*
>
>
> SQL-Server also does same like Oracle
>
> Is there any way alternate we have for same behavior in PostgreSQL
>
use function concat
http://www.postgresql.org/docs/9.5/static/functions-string.html
postgres=# select concat('AHOJ', NULL,'XXX');
concat
-
AHOJXXX
(1 row)
Regards
Pavel
> Please
>
> Thanks
> Sridhar
> OpenText
>
>
ont will be for aggregate
> functions. Experimentation might be quite simple to realise which
> functions will bring enough benefit. I imagined that even Datums where
> the type is not processor native might yield a small speedup, not from
> SIMD, but just from less calls through fmgr. P
2016-05-02 13:54 GMT+02:00 Craig Ringer :
> On 2 May 2016 at 18:51, Pavel Stehule wrote:
>
>> Hi
>>
>> what is sense of this function? There is not any comment.
>>
>>
> What it does IIRC is complain about defined GUCs nobody regi
Hi
what is sense of this function? There is not any comment.
Regards
Pavel
2016-04-25 19:40 GMT+02:00 Bruce Momjian :
>
> Good summary. Is there a TODO item here?
>
no, it is not
Regars
Pavel
>
> ---
>
> On Tue, Mar 15, 2016 at 08:17:07PM -0400, Tom Lane wrote:
>
2016-04-19 12:49 GMT+02:00 Simon Riggs :
> On 12 April 2016 at 06:51, Tom Lane wrote:
>
>> Craig Ringer writes:
>> > The other area where there's room for extension without throwing out the
>> > whole thing and rebuilding is handling of new top-level statements. We
>> can
>> > probably dispatch
2016-04-11 15:37 GMT+02:00 Merlin Moncure :
> On Sun, Apr 10, 2016 at 3:13 AM, Pavel Stehule
> wrote:
> >
> > Hi
> >
> > 2016-03-21 22:13 GMT+01:00 Pavel Stehule :
> >>
> >> Hi
> >>
> >> 2016-03-21 21:24 GMT+01:00 Merlin Mon
2016-04-18 17:44 GMT+02:00 Aleksander Alekseev :
> > It depends - can be allowed only one - like plpgsql extensions, or
> > can be serialized like pg log extensions
>
> OK, I understand "can be allowed only one". I doubt it would be a very
> useful feature though.
>
> I'm not sure what do you mean
e that these contribs will not conflict?
>
It depends - can be allowed only one - like plpgsql extensions, or can be
serialized like pg log extensions
Regards
Pavel
>
> --
> Best regards,
> Aleksander Alekseev
> http://eax.me/
>
can helps with new statements for
background workers, theoretically it can helps with extending PostgreSQL
SQL. Custom parser can do translation from SQL1 to SQL2 dialect, or can do
translation from SQL1 to internal calls. The custom parser usually should
not implement full SQL - only few stat
2016-04-16 4:12 GMT+02:00 Stephen Frost :
> Pavel,
>
> * Pavel Stehule (pavel.steh...@gmail.com) wrote:
> > 2016-04-14 14:26 GMT+02:00 Stephen Frost :
> > >
> > > * Pavel Stehule (pavel.steh...@gmail.com) wrote:
> > > > I am trying to prepare ora
2016-04-12 15:15 GMT+02:00 Pavel Stehule :
>
>
> 2016-04-12 14:51 GMT+02:00 Robert Haas :
>
>> On Tue, Apr 12, 2016 at 4:18 AM, Pavel Stehule
>> wrote:
>> > If there will be simple way, how to fix it, then I'll fix my
>> extensions. But
>> &g
Hi
2016-04-14 14:26 GMT+02:00 Stephen Frost :
> Pavel,
>
> * Pavel Stehule (pavel.steh...@gmail.com) wrote:
> > I am trying to prepare orafce for PostgreSQL 9.6.
> >
> > I can successfully compile this extension, but the statement CREATE
> > EXTENSION fails on se
2016-04-14 10:49 GMT+02:00 Peter Geoghegan :
> On Thu, Apr 14, 2016 at 1:27 AM, Pavel Stehule
> wrote:
> > (gdb) bt
> > #0 heap_deform_tuple (tuple=tuple@entry=0x1d87e90,
> > tupleDesc=tupleDesc@entry=0x7f1dab9525b0, values=values@entry=0x1d87a28,
> > isnul
fbc60) at postmaster.c:3932
This is enforced by sequence of statements REVOKE, GRANT
try to add following lines to hstore--1.3.sql
CREATE VIEW public.dual AS SELECT 'X'::varchar AS dummy;
REVOKE ALL ON public.dual FROM PUBLIC;
GRANT SELECT, REFERENCES ON public.dual TO PUBLIC;
then create extension hstore enforces this error.
When I remove the REVOKE statement - all is working.
Regards
Pavel
2016-04-12 22:48 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > I had a idea about additional options of COPY RAW statements. One can be
> > CAST function. These CAST functions can be used to any for any format.
>
> Uh, what? CAST() is not about external represent
2016-04-12 12:22 GMT+02:00 Ants Aasma :
> On 8 Apr 2016 9:14 pm, "Pavel Stehule" wrote:
> > 2016-04-08 20:54 GMT+02:00 Andrew Dunstan :
> >> I should add that I've been thinking about this some more, and that I
> now agree that something should be done to sup
2016-04-12 14:51 GMT+02:00 Robert Haas :
> On Tue, Apr 12, 2016 at 4:18 AM, Pavel Stehule
> wrote:
> > If there will be simple way, how to fix it, then I'll fix my extensions.
> But
> > new API is working only when the extension has own share memory segment.
> Fo
#x27;ll fix my extensions.
But new API is working only when the extension has own share memory
segment. For some complex extensions like Orafce it means expensive
refactoring.
What is worst, this refactoring is difficult now, because I support older
versions when I have not private shared segments.
Reg
ned for
dynamic tasks.
Regards
Pavel
>
> Понедельник, 11 апреля 2016, 16:10 +03:00 от Pavel Stehule <
> pavel.steh...@gmail.com>:
>
>
>
>
> 2016-04-11 13:11 GMT+02:00 nummervet nummervet <https://e.mail.ru/compose/?mailto=mailto%3anummer...@mail.ru>>:
>
execute $_$insert into foo values($1."123")$_$ using r;
end loop;
end;
$$;
DO
Regards
Pavel
>
> Пятница, 8 апреля 2016, 18:24 +03:00 от Pavel Stehule <
> pavel.steh...@gmail.com>:
>
>
>
>
> 2016-04-08 16:46 GMT+02:00 nummervet nummervet <htt
2016-04-10 18:49 GMT+02:00 David G. Johnston :
> On Sun, Apr 10, 2016 at 9:16 AM, Pavel Stehule
> wrote:
>
>>
>>
>> 2016-04-10 17:49 GMT+02:00 David G. Johnston
>> :
>>
>>> On Sun, Apr 10, 2016 at 1:13 AM, Pavel Stehule
>>> wrote:
>&
2016-04-10 17:49 GMT+02:00 David G. Johnston :
> On Sun, Apr 10, 2016 at 1:13 AM, Pavel Stehule
> wrote:
>
>> Hi
>>
>> 2016-03-21 22:13 GMT+01:00 Pavel Stehule :
>>
>>> Hi
>>>
>>> 2016-03-21 21:24 GMT+01:00 Merlin Moncur
Hi
2016-03-21 22:13 GMT+01:00 Pavel Stehule :
> Hi
>
> 2016-03-21 21:24 GMT+01:00 Merlin Moncure :
>
>> Patch is trivial (see below), discussion is not :-).
>>
>> I see no useful reason to require INTO when returning data with
>> SELECT. However, requiring
Hi
2016-04-08 20:54 GMT+02:00 Pavel Stehule :
>
>
> 2016-04-08 20:52 GMT+02:00 Tom Lane :
>
>> Pavel Stehule writes:
>> > 2016-04-08 17:38 GMT+02:00 Teodor Sigaev :
>> >> thank you, pushed. Pls, pay attention to buildfarm.
>>
>> > Thank
2016-04-08 20:54 GMT+02:00 Andrew Dunstan :
>
>
> On 04/08/2016 02:13 PM, Robert Haas wrote:
>
>> On Tue, Apr 5, 2016 at 4:45 AM, Pavel Stehule
>> wrote:
>>
>>> here is cleaned/finished previous implementation of RAW_TEXT/RAW_BINARY
>>> format
2016-04-08 20:52 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > 2016-04-08 17:38 GMT+02:00 Teodor Sigaev :
> >> thank you, pushed. Pls, pay attention to buildfarm.
>
> > Thank you very much for commit.
>
> According to buildfarm member prairiedog, there'
2016-04-08 17:38 GMT+02:00 Teodor Sigaev :
> Thank you very much
>>
>
> thank you, pushed. Pls, pay attention to buildfarm.
>
Thank you very much for commit.
And big thanks to Iacob for big help.
Regards
Pavel
>
> --
> Teodor Sigaev
2016-04-08 20:13 GMT+02:00 Robert Haas :
> On Tue, Apr 5, 2016 at 4:45 AM, Pavel Stehule
> wrote:
> > here is cleaned/finished previous implementation of RAW_TEXT/RAW_BINARY
> > formats for COPY statements.
> >
> > The RAW with text formats means unescaped dat
2016-04-08 16:46 GMT+02:00 nummervet nummervet :
> That didn't work for me:
>
> ERROR: syntax error at or near "$"
> LINE 1: ...ibute_id, set_id ) (select $."151", '...
>
should be $1
Regards
Pavel
>
>
> Пятница, 8 апреля 2016, 17:
( value, attribute_id, set_id )
(select $1."151", ''201'', ''1'')' using rec;
The content should be passed to dynamic query via USING clause.
http://www.postgresql.org/docs/current/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-EXECUTING-DYN
Regards
Pa
Hi
2016-04-04 7:58 GMT+02:00 Kyotaro HORIGUCHI :
> Thank you for testing. That is a silly mistake, sorry.
>
> The attached is the fixed version.
>
> # Can I add a suffix to format-patche's output files?
>
> At Sat, 2 Apr 2016 07:18:32 +0200,
ages/foo.jpg (format raw_binary);
select lastval();
create table doc(id serial, txt text);
\copy doc(txt) from ~/files/aaa.txt (format raw_text, encoding 'latin2');
select lastval();
Regards
Pavel
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
new file mode 100644
index 3829a
2016-04-02 7:16 GMT+02:00 Pavel Stehule :
> Hi
>
> 2016-04-01 10:21 GMT+02:00 Kyotaro HORIGUCHI <
> horiguchi.kyot...@lab.ntt.co.jp>:
>
>> Hello, sorry for being a bit late.
>> The attatched are the new version of the patch.. set.
>>
>> 1. 000
lding CentOS6 environment for this
> > purpose. Please wait for a while.
>
> Finally I settled it by replacing comma expression with logical
> OR or AND expresssion. gcc 4.9 compains for some unused variables
> in flex output but it is the another issue.
>
> I forgot to address COMPLETE_WITH_ATTTR but it needed an overhaul
> of some macros and changing the type of completion_charp. The
> third patch does it but it might be unacceptable..
>
>
something is wrong, autocomplete for CREATE TABLE IF NOT EXISTS doesn't work
Regards
Pavel
> regards,
>
> --
> Kyotaro Horiguchi
> NTT Open Source Software Center
>
make every effort to make emails to the list
> self-contained - which has the added benefit of avoid link expiration in
> the future.
>
> As to the recommendation at hand - I don't see significant value in
> implementing non-SQL Standard syntax in this area.
>
+1
This formula should be known to all developers
Regards
Pavel
> David J.
>
>
>
2016-04-01 4:52 GMT+02:00 Kyotaro HORIGUCHI :
> At Thu, 31 Mar 2016 11:22:20 +0200, Pavel Stehule
> wrote in <
> cafj8prd7vadunoiapb8exwc+c5ccis-rj2dphvzcwzkgxjb...@mail.gmail.com>
> > 2016-03-30 10:34 GMT+02:00 Kyotaro HORIGUCHI <
> > horiguchi.kyot..
2016-03-30 10:34 GMT+02:00 Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp>:
> Hi,
>
> At Wed, 30 Mar 2016 09:23:49 +0200, Pavel Stehule
> wrote in <
> cafj8prbvka6ng4jwz2qmro7inudfjws5w0+demvgzznuf-h...@mail.gmail.com>
> > Hi
> >
> > ...
>
2016-03-31 9:48 GMT+02:00 Craig Ringer :
> On 31 March 2016 at 14:40, Pavel Stehule wrote:
>
>
>> this patch doesn't break any old application. Accepting new feature
>> depends on binary method detection. PQbinaryTuples based clients should
>> to support COPY
2016-03-31 8:34 GMT+02:00 Craig Ringer :
> On 30 March 2016 at 00:19, Tom Lane wrote:
>
>> Pavel Stehule writes:
>> > I tested COPY RAW on old psql clients - and it is working without any
>> > problem - so when the client uses same logic as psql, then it should to
Hi
2016-03-29 20:59 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > I am writing few lines as summary:
>
> > 1. invention RAW_TEXT and RAW_BINARY
> > 2. for RAW_BINARY: PQbinaryTuples() returns 1 and PQfformat() returns 1
> > 3.a for RAW_TEXT: PQbinaryTuples() ret
ue - I don't know if it is solvable. Autocomplete
is working only for "if" keyword. When I am writing "if " or "if " or "if
exi" - then autocomplete doesn't work. But this issue is exactly same for
other "multi words" completation li
2016-03-30 5:43 GMT+02:00 Kyotaro HORIGUCHI :
> Hello,
>
> At Tue, 29 Mar 2016 13:12:06 +0200, Pavel Stehule
> wrote in kpzfw1+af_lutm...@mail.gmail.com>
> > 2016-03-29 12:08 GMT+02:00 Kyotaro HORIGUCHI <
> > > > > As mentioned before, upper-lower prob
2016-03-29 20:59 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > I am writing few lines as summary:
>
> > 1. invention RAW_TEXT and RAW_BINARY
> > 2. for RAW_BINARY: PQbinaryTuples() returns 1 and PQfformat() returns 1
> > 3.a for RAW_TEXT: PQbinaryTuples() retur
Hi
2016-03-29 18:19 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > I tested COPY RAW on old psql clients - and it is working without any
> > problem - so when the client uses same logic as psql, then it should to
> > work. Sure, there can be differently implemented
Hi
2016-03-29 0:26 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > [ copy-raw-format-20160227-03.patch ]
>
> I looked at this patch. I'm having a hard time accepting that it has
> a use-case large enough to justify it, and here's the reason: it's
> a proto
2016-03-29 12:08 GMT+02:00 Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp>:
> Hi, Pavel.
>
> At Tue, 29 Mar 2016 09:59:01 +0200, Pavel Stehule
> wrote in <
> cafj8prdepggymz2axgtl33pud7x+xieao++wa+v9nqpqiyd...@mail.gmail.com>
> > > >
Hi
2016-03-29 8:43 GMT+02:00 Kyotaro HORIGUCHI :
> Thank you Pavel, David.
>
> Thank you for pointing syntaxes to be addressed. Most of the are
> addressed in the attached patch.
>
>
> At Tue, 22 Mar 2016 12:57:27 -0400, David Steele
> wrote in <56f17977.8040...@pg
l is nice feature. And should be pretty
nice, if we support more common formats - like csv, simple xml, simple
json. I believe so sometime the redundancy is acceptable, if the cost is
not too high.
sorry for offtopic - I would to see some output format on client side, but
the format possibilities are o
Hi
2016-03-29 0:26 GMT+02:00 Tom Lane :
> Pavel Stehule writes:
> > [ copy-raw-format-20160227-03.patch ]
>
> I looked at this patch. I'm having a hard time accepting that it has
> a use-case large enough to justify it, and here's the reason: it's
> a proto
2016-03-29 5:12 GMT+02:00 Andrew Dunstan :
>
>
> On 03/28/2016 06:26 PM, Tom Lane wrote:
>
>> Pavel Stehule writes:
>>
>>> [ copy-raw-format-20160227-03.patch ]
>>>
>> I looked at this patch. I'm having a hard time accepting that it has
>
Hi
2016-03-28 6:14 GMT+02:00 Sridhar N Bamandlapally :
> Hi
>
> Is there any way to create nested function?
>
Some languages supports this feature, like plv8, but plpgsql doesn't
support it,
You have to use two function and some implementation of session variables.
Regards
2016-03-22 6:28 GMT+01:00 David Rowley :
>
> On 22/03/2016 5:24 pm, "Pavel Stehule" wrote:
> >
> > Hi
> >
> > is it expected in this moment?
> >
> >
> > Table "public.foo"
> > Column │ Type │ Modifiers
> &
2016-03-22 6:06 GMT+01:00 Tom Lane :
> Pavel Stehule writes:
> > I can live with SELECT fx(x). It is little bit dangerous, but this risk
> can
> > be easy detected by plpgsql_check.
>
> Dangerous how?
>
I afraid of useless and forgotten call of functions. But the ris
QUERY PLAN
══
Aggregate (cost=179053.25..179053.26 rows=1 width=32)
-> Seq Scan on foo2 (cost=0.00..154053.60 rows=860 width=12)
(2 rows)
Regards
Pavel
p.s. It great step forward - it looks pretty well
2016-03-21 23:49 GMT+01:00 Tom Lane :
> Jim Nasby writes:
> > On 3/21/16 5:03 PM, Merlin Moncure wrote:
> >> in Oracle, you'd simply do:
> >> LogIt('I did something');
>
> > It would be *great* if we could support that in plpgsql.
>
> FWIW, I'm hesitant to just start accepting that syntax as if i
. worked
> too.
>
We are support
var := (query expression)
and this syntax is required and supported by ANSI/SQL - there are no any
reason to support other proprietary extension.
Regards
Pavel
>
> I'm not sure what other databases do is relevant. They use other
>> pr
2016-03-21 23:03 GMT+01:00 Merlin Moncure :
> On Mon, Mar 21, 2016 at 4:13 PM, Pavel Stehule
> wrote:
> > Hi
> >
> > 2016-03-21 21:24 GMT+01:00 Merlin Moncure :
> >>
> >> Patch is trivial (see below), discussion is not :-).
> >>
> >>
the result in a variable (for example passing to
> volatile function). Take a look at the errhint() clause below -- we
> don't even have a suggestion in that case.
>
> This has come up before, and there was a fair amount of sympathy for
> this argument albeit with some dissent -
Hi
2016-03-19 16:31 GMT+01:00 Alvaro Herrera :
> Pavel Stehule wrote:
>
> > Can I do review?
>
> Of course.
>
I did review of last patch. I had to do small changes to run the code due
last Tom's changes in psql. Updated patch is attached.
The last changes in this
2016-03-18 16:26 GMT+01:00 Teodor Sigaev :
> I hope so the messages are ok now. Few more regress tests added.
>>
>
> Thank you, committed.
Thank you very much
Pavel
>
>
> --
> Teodor Sigaev
Thank you!
>
great, important feature
Thank you
Pavel
> --
> Vik Fearing +33 6 46 75 15 36
> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@
2016-03-18 16:32 GMT+01:00 David Steele :
> On 3/12/16 1:24 AM, Pavel Stehule wrote:
>
> Great, thank you very much. I hope so this feature really useful. It
>> allow to simple export/import XML doc in different encodings, JSONs and
>> can be enhanced future via options. T
2016-03-16 20:53 GMT+01:00 Jim Nasby :
> On 3/3/16 4:51 AM, Pavel Stehule wrote:
>
>> CREATE TABLE a(a int);
>> CREATE TABLE b(a a.a%TYPE)
>>
>> And the people expecting the living relation between table a and table
>> b. So when I do ALTER a.a, then b.a shou
> Dean, Tom, Peter, what do you think of the new version?
>
> Is anyone up for re-reviewing this? If not, I think we're going to
> have to reject this for lack of interest.
>
Can I do review?
Pavel
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Hi
2016-03-17 21:02 GMT+01:00 Pavel Stehule :
> Hi
>
>
> I am looking this patch. It looks well, but this feature doesn't respect
> upper or lower chars. It enforce upper chars. This is not consistent with
> any other autocomplete.
>
I checked it against sql help an
e extended later if we think of other type operators we want.
>
> +1
>
> Anyone want to argue against changing the status of this to Rejected or
> at least Returned with feedback?
>
I would to reduce this patch to fix row type issue. There is not any
disagreement. I'll send r
2016-03-17 1:02 GMT+01:00 David G. Johnston :
> On Wed, Mar 16, 2016 at 4:39 PM, Tom Lane wrote:
>
>> Jim Nasby writes:
>> > On 3/3/16 4:51 AM, Pavel Stehule wrote:
>> >> CREATE TABLE a(a int);
>> >> CREATE TABLE b(a a.a%TYPE)
>> >>
&
2016-03-17 0:39 GMT+01:00 Tom Lane :
> Jim Nasby writes:
> > On 3/3/16 4:51 AM, Pavel Stehule wrote:
> >> CREATE TABLE a(a int);
> >> CREATE TABLE b(a a.a%TYPE)
> >>
> >> And the people expecting the living relation between table a and table
>
Hi
2016-03-13 20:24 GMT+01:00 Jim Nasby :
> On 3/3/16 8:51 AM, Pavel Stehule wrote:
>
>> Hi
>>
>> I am testing behave, and some results looks strange
>>
>
> Thanks for the review!
>
> postgres=# \sf foo
>> CREATE OR REPLACE FUNCTION public.foo
ot;c"
>
> Error message wrongly points to the reason of error.
>
>
I forgot my original plan - show full original string. Now, complete
original parameter is used as part of message everywhere. It is more
consistent.
I cannot to reuse escape_json - it escape double quotes, and t
801 - 900 of 5265 matches
Mail list logo
