On Wed, Apr 13, 2016 at 3:53 PM, Stephen Frost wrote:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > Stephen Frost writes:
> > > On Wednesday, April 13, 2016, Tom Lane wrote:
> > >> If you want to prevent that, I think it needs to be done somewhere
> else
> > >> than here. What about "ALTER OWNE
On Wed, Apr 13, 2016 at 3:48 PM, Daniel Lenski wrote:
> On Wed, Apr 13, 2016 at 12:35 PM, Tom Lane wrote:
> > Jim Nasby writes:
> >> Actually, after looking at the code for interval_lt, all that needs to
> >> happen to add this support is to expose interval_cmp_internal() as a
> >> strict funct
On Wed, Apr 13, 2016 at 12:29 PM, Tom Lane wrote:
> Christoph Berg writes:
> > Another thing about \crosstabview:
>
> > # select 1,2 \crosstabview
> > The query must return at least two columns to be shown in crosstab
>
> > s/two/three/, I guess.
>
> Yeah, I noticed that. See
> http://www.postg
On Tue, Apr 12, 2016 at 2:04 PM, Robert Haas wrote:
> On Tue, Apr 12, 2016 at 4:32 PM, David G. Johnston
> wrote:
> > I give a solid +10 to Robert's opinions on the matter and aside from
> > figuring out if and how to fit first-number versioning dynamics into our
>
On Tue, Apr 12, 2016 at 1:07 PM, Oleg Bartunov wrote:
>
>
>> * we don't *know* that any of the above items will require a backwards
>> compatibility break.
>>
>> People keep talking about "we might want to break compatibility/file
>> format one day". But nobody is working on anything which will
On Mon, Apr 11, 2016 at 9:58 PM, Tsunakawa, Takayuki <
tsunakawa.ta...@jp.fujitsu.com> wrote:
> *From:* pgsql-hackers-ow...@postgresql.org [mailto:
> pgsql-hackers-ow...@postgresql.org] * On Behalf Of *Arcadiy Ivanov
>
> Currently the parser and lexer are fully fixed at compile-time and not
> amen
On Sun, Apr 10, 2016 at 10:01 AM, Pavel Stehule
wrote:
>
>
> 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 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:
>>
>>> Hi
>>>
>>> 2016-03-21 22:13 GMT+01:00 Pavel Stehule :
>&g
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 Moncure :
>>
>>> Patch is trivial (see below), discussion is not :-).
>>>
>>> I see no useful reason to require INTO when returning data with
>
On Thu, Apr 7, 2016 at 1:26 PM, Alvaro Herrera
wrote:
> I wonder if the business of appending values of multiple columns
> separated with spaces is doing us any good. Why not require that
> there's a single column in the cell? If the user wants to put things
> together, they can use format() or
On Fri, Apr 1, 2016 at 8:42 AM, Daniel Verite
wrote:
> Andrew Dunstan wrote:
>
> > If someone can make a good case that this is going to be of
> > general use I'll happily go along, but I haven't seen one so far.
>
> About COPY FROM with a raw format, for instance just yesterday
> there w
On Sun, Apr 3, 2016 at 10:18 PM, Simon Riggs wrote:
> On 4 April 2016 at 01:14, Michael Paquier
> wrote:
>
>
>> I'd say why not.
>>
>
> I'd say "why not wait?". Minor, non-urgent patches will definitely go
> nowhere for a long time, so it gains nobody to submit now.
>
> Submitting patches during
On Sun, Apr 3, 2016 at 9:49 PM, Igal @ Lucee.org wrote:
> On 4/3/2016 4:34 PM, Dave Cramer wrote:
>
>
> On 4/3/2016 8:21 AM, Dave Cramer wrote:
>
>>
>> I'd like to turn this question around. Are there good reasons to use -ng
>> over pgjdbc ?
>>
>> As to your question, you may be interested to kno
On Fri, Apr 1, 2016 at 3:22 PM, Jim Nasby wrote:
> On 4/1/16 1:08 PM, Tom Lane wrote:
>
>> Jim Nasby writes:
>>
>>> Rather than this, I think an exclusive-or operator would be a lot more
>>> useful. The only difficulty I run into with CHECK constaints is when I
>>> want to ensure that only ONE c
On Thu, Mar 31, 2016 at 10:19 AM, Alexander Ostrow wrote:
> Hello,
>
> I thought it would be cool to have conditional check syntax, which gets
> converted to simple check constraint syntax.
>
> Here’s a gist:
>
> https://gist.github.com/aj0strow/5a07f2ddcad324c4dac2c4095c821999
>
> It’s just suga
On Sun, Mar 27, 2016 at 9:14 PM, Sridhar N Bamandlapally <
sridhar@gmail.com> wrote:
> Hi
>
> Is there any way to create nested function?
>
> oracle to postgres migration required super function variable reference
> into nested function without nested function parameter
>
> Oracle sample:
> --
On Sun, Mar 27, 2016 at 8:43 PM, Peter Geoghegan wrote:
> On Sat, Mar 26, 2016 at 4:34 PM, Tom Lane wrote:
> > Probably the most discussion-worthy item is whether we can say
> > anything more about the strxfrm mess. Should we make a wiki
> > page about that and have the release note item link t
On Friday, March 25, 2016, Andrew Dunstan wrote:
>
> On 03/25/2016 04:13 AM, Matthias Kurz wrote:
>
>>
>> Hopefully at the commitfest at least the transaction limitation
>> will/could be tackled - that would help us a lot already.
>>
>>
> I don't believe anyone knows how to do that safely. Enums
On Wed, Mar 23, 2016 at 2:11 PM, Tom Lane wrote:
>
>
> In the meantime I suppose there's a case to be made for preserving
> bug compatibility as much as possible.
>
> So anyway the question is whether to commit the attached or not.
+1 for commit - I'll trust Tom on the quality of the patch
On Wednesday, March 23, 2016, Tom Lane wrote:
> "Regina Obe" > writes:
> > In the past couple of weeks our PostGIS tests against PostgreSQL 9.6 dev
> > started failing. I traced the issue down to a behavior change in 9.6
> when
> > dealing with output of set returning functions when used with (f
Please don't top-post.
On Tuesday, March 22, 2016, Peter Krauss wrote:
> Subjective notes to contextualize (try to explain on bad-English) my
> "precedence order" and JSONB visions:
>
> JSON datatype is perfect as workaround, and for many simple and less
> exigent applications.
> JSONB is the "
On Tue, Mar 22, 2016 at 1:52 PM, Peter Krauss wrote:
> Seems that parser not using precedence ideal order, and that casting
> obligation losts performance.
>
> The first problem is self-evident in this example:
>
> SELECT '{"x":1}'::jsonb || (('{"A":{"y":2}}'::jsonb)->'A')
> -- it is ok, expect
On Monday, March 21, 2016, Tom Lane wrote:
> "David G. Johnston" > writes:
> > On Monday, March 21, 2016, Tom Lane >
> wrote:
> >> What about just discarding the old format entirely, and printing one of
> >> these two things:
> >>
> >
On Monday, March 21, 2016, Tom Lane wrote:
> "David G. Johnston" > writes:
> > I'll admit it's awkward because it's abbreviated but if someone enters
> > \watch 5 and then sees (5s) in the title I think they can put two and two
> > together.
>
On Monday, March 21, 2016, Robert Haas wrote:
> On Mon, Mar 21, 2016 at 2:09 PM, David G. Johnston
> > wrote:
> > On Monday, March 21, 2016, Tom Lane >
> wrote:
> >> "David G. Johnston" > writes:
> >> > I'd rather not omit sleep but
On Monday, March 21, 2016, Tom Lane wrote:
> "David G. Johnston" > writes:
> > I'd rather not omit sleep but removing "Watch every" is fine (preferred
> > actually), so:
> > Title Is Here Mon Mar 21 15:05:06 2016 (5s)
>
> Meh ... seem
On Mon, Mar 21, 2016 at 10:14 AM, Tom Lane wrote:
> Robert Haas writes:
> > Well, the title isn't normally centered, but yeah, that is odd. Yeah,
> > that is odd. Come to think of it, I think I might have expected the
> > title to appear *above* "Watch every %s", not below it. That might
> >
On Mon, Mar 21, 2016 at 8:03 AM, Robert Haas wrote:
> On Sun, Mar 20, 2016 at 9:31 AM, Michael Paquier
> wrote:
> > And the patch attached gives the following output:
> > With title:
> > =# \watch 1
> > Watch every 1sSun Mar 20 22:28:38 2016
> > popo
> > a
> > ---
> > 1
> > (1 row)
>
Thi
On Sunday, March 20, 2016, Tom Lane wrote:
>
> * Allow backslash commands to span lines, probably by adopting the
> rule that backslash immediately followed by newline is to be ignored
> within a backslash command. This would not be compatible with psql,
> though, at least not unless we wanted t
On Thursday, March 17, 2016, Robert Haas wrote:
> On Thu, Mar 17, 2016 at 6:34 PM, Chapman Flack > wrote:
> > For those of us who are outside of the twitterverse sort of on purpose,
> > are there a few representative links you could post? Maybe this is such
> > fresh breaking news Google hasn't
On Thu, Mar 17, 2016 at 7:57 AM, Corey Huinker
wrote:
> On Thu, Mar 17, 2016 at 10:00 AM, David Steele
> wrote:
>
>> On 3/17/16 4:49 AM, Dean Rasheed wrote:
>>
>> > On 16 March 2016 at 23:32, David Steele wrote:
>> >
>> >>
>> >> I think in this case it comes down to a committer's judgement so I
On Thu, Mar 17, 2016 at 2:17 PM, Gavin Flower wrote:
> On 18/03/16 09:41, Joshua D. Drake wrote:
>
>> On 03/17/2016 01:36 PM, Alvaro Herrera wrote:
>>
>> [...]
>
>>
>>
>>> (*) I'm probably going to be expelled from the project for saying this,
>>> but I very much doubt that female coders stay awa
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)
> >>
> >> And the people expecting the living relation between table a and table
> >> b. So when I do ALTER a.a, then b.a s
On Thursday, March 17, 2016, Michael Paquier
wrote:
> On Fri, Mar 18, 2016 at 8:16 AM, Tom Lane > wrote:
> > David Steele > writes:
> >> On 3/17/16 7:00 PM, Tom Lane wrote:
> >>> The message I saw was post-1-March. If it was in fact submitted in
> >>> time for 2016-03, then we owe it a review.
Figured out it had to be added to 2016-09...done
On Wed, Mar 9, 2016 at 11:40 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> Adding -hackers for consideration in the Commitfest.
>
> Thanks!
>
> David J.
>
> >>>Original request by me
>
&
On Thu, Mar 17, 2016 at 8:41 AM, David Steele wrote:
> On 3/17/16 11:30 AM, David G. Johnston wrote:
> > On Thu, Mar 17, 2016 at 7:57 AM, Corey Huinker > <mailto:corey.huin...@gmail.com>>wrote:
> >
> > On Thu, Mar 17, 2016 at 10:00 AM, David Steele >
On Saturday, March 12, 2016, David G. Johnston
wrote:
> On Saturday, March 12, 2016, Tom Lane > wrote:
>
>> "David G. Johnston" writes:
>> > Don't the semantics of a SEMI JOIN also state that the output columns
>> only
>> > come fro
On Saturday, March 12, 2016, Tom Lane wrote:
> "David G. Johnston" > writes:
> > Don't the semantics of a SEMI JOIN also state that the output columns
> only
> > come from the outer relation? i.e., the inner relation doesn't contribute
> > either r
On Saturday, March 12, 2016, David Rowley
wrote:
> On 12 March 2016 at 11:43, Tom Lane >
> wrote:
> > I wrote:
> >> I wondered why, instead of inventing an extra semantics-modifying flag,
> >> we couldn't just change the jointype to *be* JOIN_SEMI when we've
> >> discovered that the inner side is
On Fri, Mar 11, 2016 at 4:45 PM, Koichi Suzuki wrote:
> Hi,
>
> Does someone know how to prepare a synamic SQL statement in plpgsql?
>
> All the examples, PG documents describe only about preparing static SQL
> statement.
>
>
This is not an appropriate question for the -hackers list. It is bette
On Fri, Mar 11, 2016 at 4:45 PM, Koichi Suzuki wrote:
> Hi,
>
> Does someone know how to prepare a synamic SQL statement in plpgsql?
>
> All the examples, PG documents describe only about preparing static SQL
> statement.
>
>
You might want to rephrase the question. From the pl/pgsql documentati
On Thu, Mar 10, 2016 at 11:45 AM, Robert Haas wrote:
> On Thu, Mar 10, 2016 at 11:33 AM, David G. Johnston
> wrote:
> > I tend to think we err toward this too much. This seems like development
> > concerns trumping usability. Consider that anything someone took the
>
On Thu, Mar 10, 2016 at 9:30 AM, Michael Paquier
wrote:
> On Thu, Mar 10, 2016 at 4:58 PM, Robert Haas
> wrote:
> > On Thu, Mar 10, 2016 at 10:30 AM, Simon Riggs
> wrote:
> >> On 10 March 2016 at 06:53, Michael Paquier
> >> wrote:
> >>>
> >>> On Wed, Mar 9, 2016 at 12:13 AM, Alvaro Herrera
> >
On Thu, Mar 10, 2016 at 8:58 AM, Robert Haas wrote:
> On Thu, Mar 10, 2016 at 10:30 AM, Simon Riggs
> wrote:
> > On 10 March 2016 at 06:53, Michael Paquier
> > wrote:
> >>
> >> On Wed, Mar 9, 2016 at 12:13 AM, Alvaro Herrera
> >> wrote:
> >> > Robert Haas wrote:
> >> >> I'm pretty meh about th
tion into the title.
-- Forwarded message --
From: Michael Paquier
Date: Thu, Jan 28, 2016 at 6:01 AM
Subject: Re: [GENERAL] Request - repeat value of \pset title during \watch
interations
To: "David G. Johnston"
Cc: Tom Lane , "pgsql-gene...@postgresql.org" &
On Tue, Mar 8, 2016 at 3:57 PM, Corey Huinker
wrote:
>
>> I'm pretty meh about the whole idea of this function, though,
>> actually, and I don't see a single clear +1 vote for this
>> functionality upthread. (Apologies if I've missed one.) In the
>> absence of a few of those, I recommend we rej
Placing this specific message onto -bugs while keeping -hackers and
removing -novice.
Editing subject to include version and remove list identifiers.
There is continuing discussion on -hackers though mostly about how to do
this right in the future. The specific problem stems from an attempted
pe
On Wed, Mar 2, 2016 at 2:44 PM, Joe Conway wrote:
> On 03/02/2016 12:54 PM, Stephen Frost wrote:
> > * Joe Conway (m...@joeconway.com) wrote:
> >> On 03/01/2016 08:00 AM, Tom Lane wrote:
> >>> Yes, we'd need some way to mark non-null ACLs as being "built-in
> >>> defaults". I do not see the need
On Wed, Mar 2, 2016 at 1:54 PM, Stephen Frost wrote:
> * Joe Conway (m...@joeconway.com) wrote:
> > On 03/01/2016 08:00 AM, Tom Lane wrote:
> > > Joe Conway writes:
> > >> Would it be a terrible idea to add some attribute to ACLs which can be
> > >> used to indicate they should not be dumped (an
On Tue, Feb 23, 2016 at 9:43 AM, Bruce Momjian wrote:
> 4. Cross-node read-write queries:
>
> This will require a global snapshot manager and global snapshot manager.
>
Probably meant "global transaction manager"
David J.
On Mon, Feb 15, 2016 at 4:23 PM, Tatsuo Ishii wrote:
> While reading planstats.sgml, I encounted a sentence which I don't
> understand.
>
> These numbers are current as of the last VACUUM or
> ANALYZE on the table. The planner then fetches the
> actual current number of pages in the
On Thu, Feb 11, 2016 at 10:53 AM, Pavel Stehule
wrote:
> > most recent error in verbose mode, without making a permanent session
>
>> > state change. Something like
>> >
>> > regression=# insert into bar values(1);
>> > ERROR: insert or update on table "bar" violates foreign key constraint
>> "
On Tue, Feb 9, 2016 at 11:32 AM, Corey Huinker
wrote:
>
> Oh, and I suggest we call them SESSION variables rather than SCHEMA
> variables, to reinforce the idea of how long the values in the variables
> live. A session variable is in a sense a 1x1 temp table, whose definition
> persists across se
On Monday, February 8, 2016, Andres Freund wrote:
> Hi,
>
> On 2016-02-08 16:07:05 -0500, Robert Haas wrote:
> > One of the questions I have about parallel query is whether it should
> > be enabled by default. That is, should we make the default value of
> > max_parallel_degree to a value higher
On Thu, Feb 4, 2016 at 3:57 PM, Alvaro Herrera
wrote:
> David G. Johnston wrote:
>
> > Learning by reading here...
> >
> > http://www.postgresql.org/docs/current/static/wal-internals.html
> > """
> > After a checkpoint has been made and the
On Wed, Feb 3, 2016 at 9:36 AM, Robert Haas wrote:
> On Wed, Feb 3, 2016 at 10:37 AM, David Steele wrote:
> > On 2/1/16 11:23 PM, Robert Haas wrote:
>
> >> In
> >> saying that it's arbitrary, I'm not saying it isn't *useful*. I'm
> >> saying there could be five extensions like this that make eq
So, Noah's excellent response has been ignored (from what my threaded
Gmail view tells me) at this point...
On Tue, Feb 2, 2016 at 6:25 PM, Curtis Ruck <
curtis.ruck+pgsql.hack...@gmail.com> wrote:
> Robert,
>
> This isn't wrong. I don't see anyone else trying to submit anything in
> reference
On Mon, Feb 1, 2016 at 5:48 PM, Andres Freund wrote:
> On 2016-02-01 17:29:39 -0700, David G. Johnston wrote:
> > Learning by reading here...
> >
> > http://www.postgresql.org/docs/current/static/wal-internals.html
> > """
> > After a c
On Mon, Feb 1, 2016 at 4:58 PM, Andres Freund wrote:
> Hi,
>
> currently if, when not in standby mode, we can't read a checkpoint
> record, we automatically fall back to the previous checkpoint, and start
> replay from there.
>
> Doing so without user intervention doesn't actually seem like a goo
On Thu, Jan 28, 2016 at 7:48 AM, Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> Robert>Hmm, so in your example, you actually want replanning to be able to
> Robert>change the cached plan's result type?
>
> I want backend to cache _several_ plans behind a single "statement name".
> I wan
On Monday, January 25, 2016, Vladimir Sitnikov
wrote:
> I want to treat 'prepare' operation as an optimization step, so it is
> functionally equivalent to sending a query text.
>
> In other words, I would like backend to track search_path and other
> parameters if necessary transparently, creati
On Fri, Jan 15, 2016 at 7:49 AM, Tom Lane wrote:
> Abhijit Menon-Sen writes:
> > I'm looking at an extension that creates some triggers (on user tables)
> > dynamically (i.e., not during CREATE EXTENSION, but afterwards). The
> > author has two problems with it:
>
>
How do these triggers come to
On Thu, Jan 14, 2016 at 1:25 PM, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Thu, Jan 14, 2016 at 1:07 PM, Tom Lane wrote:
> >> Vitaly Burovoy writes:
> >>> You can't now do something like
> >>> INSERT INTO foo (arraycol[2]
On Thu, Jan 14, 2016 at 1:07 PM, Tom Lane wrote:
> Vitaly Burovoy writes:
> > On 1/14/16, Tom Lane wrote:
> >> It's more than syntactic sugar; you are going to have to invent
> semantics,
> >> as well, because it's less than clear what partial-field assignments
> >> should do.
> >>
> >> Assume
On Fri, Dec 18, 2015 at 10:25 AM, Tom Lane wrote:
> Robert Haas writes:
> > On Fri, Dec 18, 2015 at 12:10 PM, Andres Freund
> wrote:
> >> I'm saying that 10 year deprecation periods don't make sense. Either we
> >> decide to remove the compat switch because we dislike it for $reasons,
> >> in w
On Tue, Dec 8, 2015 at 12:36 PM, Robert Haas wrote:
> On Wed, Dec 2, 2015 at 5:24 PM, Tom Lane wrote:
> > Jeff Janes writes:
> >> On Wed, Dec 2, 2015 at 12:37 PM, Josh Berkus wrote:
> >>> If you're fixing the dashed-line code, is there a way to say that we
> >>> never have more than a reasonab
On Tue, Dec 8, 2015 at 4:43 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Tue, Dec 8, 2015 at 3:33 AM, FattahRozzaq wrote:
>
>> Hi all,
>>
>> Please help...
>>
>> I have 1 master PostgreSQL and 1 standby PostgreSQL.
>> Both serve
On Tue, Dec 8, 2015 at 3:33 AM, FattahRozzaq wrote:
> Hi all,
>
> Please help...
>
> I have 1 master PostgreSQL and 1 standby PostgreSQL.
> Both servers has the same OS Linux Debian Wheezy, the same hardware.
>
> Both server hardware:
> CPU: 24 cores
> RAM: 128GB
> Disk-1: 800GB SAS (for OS, logs
On Mon, Dec 7, 2015 at 8:35 AM, Jim Nasby wrote:
> On 12/6/15 10:38 AM, Tom Lane wrote:
>
>> I said "in most cases". You can find example cases to support almost any
>> weird planner optimization no matter how expensive and single-purpose;
>> but that is the wrong way to think about it. What yo
On Wed, Dec 2, 2015 at 11:04 AM, Robert Haas wrote:
> On Wed, Dec 2, 2015 at 11:07 AM, Tom Lane wrote:
> > I just noticed that parse_psql_options() ignores the result of
> setQFout(),
> > meaning that if the argument of a -o command line option is bogus, we'll
> > ignore the switch entirely afte
On Fri, Nov 13, 2015 at 1:54 PM, Catalin Iacob
wrote:
> So I promised I'd try to document this. I had a look at the proposed
> semantics of -C and I think in the patch they're too complicated which
> makes explaining them hard.
>
> My assumptions about behaviour without this patch, from reading t
On Thu, Nov 12, 2015 at 1:04 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thu, Oct 29, 2015 at 6:50 AM, Tom Lane wrote:
>
>> Marko Tiikkaja writes:
>> > On 10/29/15 11:51 AM, Daniel Verite wrote:
>> >> Personally I think it would be wor
On Thu, Oct 29, 2015 at 6:50 AM, Tom Lane wrote:
> Marko Tiikkaja writes:
> > On 10/29/15 11:51 AM, Daniel Verite wrote:
> >> Personally I think it would be worth having, but how about
> >> booleans inside ROW() or composite types ?
>
> > There's not enough information sent over to do that in th
On Thu, Oct 29, 2015 at 5:28 AM, Matthijs van der Vleuten
wrote:
> I have had exactly this situation a week ago. I was testing the output of
> an algorithm that is supposed to have exactly one true value per input id.
>
If this is particularly important I would add something like (and(col1,
col
On Wed, Nov 11, 2015 at 7:01 AM, Michael Paquier
wrote:
> It seems to me that the documentation should specify that when -C is
> used with -1 each individual series of commands is executed within a
> transaction block.
In summary:
Default (Not Single + Auto-Commit): One Transactions per parse
On Fri, Nov 6, 2015 at 7:32 PM, Tom Lane wrote:
> What I'm wondering about is whether to back-patch this. It's possible
> that people have written patterns like this and not realized that they
> aren't doing quite what's expected. Getting a failure instead might not
> be desirable in a minor re
On Thursday, November 5, 2015, Craig Ringer wrote:
> On 6 November 2015 at 12:45, Robert Haas > wrote:
> > On Thu, Nov 5, 2015 at 9:57 AM, YUriy Zhuravlev
> > > wrote:
> >> Hello hackers.
> >> There are comments to my patch? Maybe I should create a separate thread?
> >> Thanks.
> >
> > You shoul
On Thu, Nov 5, 2015 at 2:15 PM, Robert Haas wrote:
> On Thu, Nov 5, 2015 at 6:20 AM, Haribabu Kommi
> wrote:
> > I went through the patch, following are my observations,
> >
> > Patch applied with hunks and compiled with out warnings.
> > Basic tests are passed.
>
> I'm interested in hearing opi
On Wed, Oct 28, 2015 at 1:38 PM, Tom Lane wrote:
> Marko Tiikkaja writes:
> > Here's a patch for the aggregate function outlined by Corey Huinker in
> > CADkLM=foA_oC_Ri23F9PbfLnfwXFbC3Lt8bBzRu3=cb77g9...@mail.gmail.com . I
> > called it "onlyvalue", which is a horrible name, but I have nothing
On Thu, Oct 22, 2015 at 7:05 PM, Tom Lane wrote:
> I think it's already true that the previous lines of the query buffer
> are stashed somewhere that psql knows about,
Just skimming but:
"""
\p or \print
Print the current query buffer to the standard output.
"""
http://www.postgresql.org/
On Friday, October 16, 2015, Tom Lane wrote:
>
> Anyway, I'm not planning to do much more work on this right now, but
> I thought I'd throw it out there just to let people know that this seems
> within reach. I'm curious to know how many people care, and how much.
>
>
+1
It's hard to quantify h
>
>
>> > Using this attribute, we can have more control on parallel operations
>> like,
>>
>> > IF SKIPPED_ROW_COUNT =0 THEN
>> > <>
>> > ELSE
>> > <>
>> > END IF;
>>
>> Um ... so what? This is not a use-case.
>>
>>
> In my view, "How one can be sure that, he obtained all the tuples with
> SKIP LO
On Wed, Sep 30, 2015 at 5:49 PM, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Wed, Sep 30, 2015 at 2:52 PM, Joe Conway wrote:
> >> I was looking at something in gram.y when I noticed that the following
> >> production works:
> >> SET SESSI
On Wed, Sep 30, 2015 at 2:52 PM, Joe Conway wrote:
> I was looking at something in gram.y when I noticed that the following
> production works:
>
>
> SET SESSION SESSION CHARACTERISTICS AS TRANSACTION READ ONLY;
>
>
> "SESSION SESSION" seems fairly odd -- is it intentional?
>
Scanning the SET a
On Wed, Sep 23, 2015 at 5:10 PM, Szymon Lipiński wrote:
>
>
> On 23 September 2015 at 22:07, Stephen Frost wrote:
>
>> * Josh Berkus (j...@agliodbs.com) wrote:
>> > On 09/23/2015 11:18 AM, Kam Lasater wrote:
>> > > At this point not having one is borderline negligent. I'd suggest:
>> > > Github
On Wed, Sep 23, 2015 at 5:00 PM, Stephen Frost wrote:
> Kam,
>
> * Kam Lasater (c...@seekayel.com) wrote:
> > > ... The above-referenced individuals
> > > would be the bug tracking system curators, of course. Unless it's got
> > > serious technical issues, the infrastructure team will do our bes
On Wed, Sep 9, 2015 at 7:53 PM, Charles Sheridan wrote:
> Hi All,
>
> When there are several views defined on top of each other, are SELECTs on
> views that do not specify a SORT order guaranteed to preserve the
> cumulative sort order of the lower-level views ?
>
> Is the answer true for any arb
On Tue, Sep 8, 2015 at 1:38 PM, Robert Haas wrote:
> On Mon, Sep 7, 2015 at 5:08 PM, David G. Johnston
> wrote:
> > Given the role that psql performs I do think \rotate to be the least
> > problematic choice; I concur that avoiding \pivot is desirable due to
> SQL's
&g
On Mon, Sep 7, 2015 at 4:18 PM, Pavel Stehule
wrote:
>
>
> 2015-09-07 22:14 GMT+02:00 Greg Stark :
>
>> On Fri, Sep 4, 2015 at 5:08 PM, Daniel Verite
>> wrote:
>> > I'm not dead set on \rotate and suggested other names
>> > previously in [1], but none of them seems decisively
>> > superior.
>>
>
On Mon, Aug 31, 2015 at 10:39 AM, Shulgin, Oleksandr <
oleksandr.shul...@zalando.de> wrote:
> On Mon, Aug 31, 2015 at 4:01 PM, Tom Lane wrote:
>
>>
>> It'll be a real
>> mess if we do that for everything.
>>
>
> I share the fear that it could become messy, but it doesn't necessary
> *have to* be
On Mon, Aug 31, 2015 at 10:20 AM, Kevin Grittner wrote:
> Pavel Raiskup wrote:
>
> > It's been reported [1] that postmaster fails to start against staled
> > postmaster.pid after (e.g.) power outage on Fedora, its due to init
> system
> > parallelism and "some" other newly started process can al
On Sat, Aug 29, 2015 at 4:27 PM, Tom Lane wrote:
> Jim Nasby writes:
> > On 8/29/15 12:29 PM, Pavel Stehule wrote:
> >> what is correct from JSON perspective? All fields with NULL
>
> > ISTM that the whole purpose of to_json is to properly jsonify something,
> > and the proper json form for "und
On Fri, Aug 28, 2015 at 4:18 PM, Pavel Stehule
wrote:
>
>
> 2015-08-28 22:07 GMT+02:00 Jim Nasby :
>
>> On 8/26/15 8:15 AM, Pavel Stehule wrote:
>>
>>> + and then exit. This is useful in shell scripts. Start-up files
>>> + (psqlrc and ~/.psqlrc)
>>> are
>>> + ignored with this opti
On Fri, Aug 28, 2015 at 4:07 PM, Jim Nasby wrote:
> On 8/26/15 8:15 AM, Pavel Stehule wrote:
>
>> + and then exit. This is useful in shell scripts. Start-up files
>> + (psqlrc and ~/.psqlrc)
>> are
>> + ignored with this option.
>>
>
> Sorry if this was discussed and I missed it, b
Pure speculation but the word fire makes me think of triggers, not rule.
Fire Referential Integrity Rules (Triggers)?
David J.
On Thu, Aug 27, 2015 at 9:13 AM, Andres Freund wrote:
> Hi,
>
> I searched the current code, all diffs to the current code, and the
> mailing list, but still haven't g
On Tue, Aug 25, 2015 at 6:21 PM, Jim Nasby wrote:
> This works:
>
> CREATE TYPE c AS (r float, i float);
> CREATE FUNCTION mag(c c) RETURNS float LANGUAGE sql AS $$
> SELECT sqrt(c.r^2 + c.i^2)
> $$;
> SELECT mag( (2.2, 2.2) );
>mag
> --
> 3.11126983722081
>
> But this do
On Fri, Aug 14, 2015 at 6:11 PM, Dickson S. Guedes
wrote:
> 2015-08-14 21:40 GMT-03:00 David G. Johnston :
> > On Friday, August 14, 2015, Dickson S. Guedes
> wrote:
> >>
> >>
> >> The term is used in a school or college to represent a half-year.
> >
On Friday, August 14, 2015, Dickson S. Guedes wrote:
>
> The term is used in a school or college to represent a half-year.
> Actually it could be evaluated from a date using some math with
> 'quarter' but could not be extracted from date since the API to define
> a "reserved word" for EXTRACT is
On Wed, Aug 12, 2015 at 4:11 PM, Tom Lane wrote:
> Peter Geoghegan writes:
> > On Wed, Aug 12, 2015 at 10:30 AM, Alvaro Herrera
> > wrote:
> >> The name count_nulls() suggest an aggregate function to me, though.
>
> > I thought the same.
>
> Ditto. I'd be fine with this if we can come up with
On Saturday, July 25, 2015, Pavel Stehule wrote:
>
> 2015-07-23 17:52 GMT+02:00 Robert Haas :
>
>> On Fri, Jul 17, 2015 at 12:36 AM, Pavel Stehule
>> wrote:
>> >> Or just properly understand the ; ?
>> >>
>> >> -c "select * from foo; update bar set baz = 'bing'; vacuum bar;"
>> >
>> > there is a
301 - 400 of 608 matches
Mail list logo
