> On Tue, Oct 20, 2015 at 12:39 PM, Etsuro Fujita
> wrote:
> > Sorry, my explanation was not correct. (Needed to take in caffeine.) What
> > I'm concerned about is the following:
> >
> > SELECT * FROM localtab JOIN (ft1 LEFT JOIN ft2 ON ft1.x = ft2.x) ON
> > localtab.id = ft1.id FOR UPDATE OF ft1
The security_barrier view option is classified as string in the create
view documentation.
But it is actually a boolean. The type is mentioned correctly in alter
view. Here I attached
the patch with the correction.
-security_barrier (string)
+security_barrier (boolean)
Regards,
Ha
On Tue, Oct 27, 2015 at 05:31:25PM +0900, Tatsuo Ishii wrote:
> > No, PQping("host='127.0.0.1'") fails to reach a listen_addresses='::' server
> > on many systems. Here's what I thought Kondo was proposing:
> >
> > --- a/src/bin/pg_ctl/pg_ctl.c
> > +++ b/src/bin/pg_ctl/pg_ctl.c
> > @@ -649,5 +649
David Rowley writes:
> I just found myself in execScan.c. I noticed that tlist_matches_tupdesc()
> is a bit wasteful in some cases as it goes to the trouble of matching the
> tlist to the TupleDesc item by item until it runs out of tlist items
> or finds a non-match. Once the loop completes it ens
I just found myself in execScan.c. I noticed that tlist_matches_tupdesc()
is a bit wasteful in some cases as it goes to the trouble of matching the
tlist to the TupleDesc item by item until it runs out of tlist items
or finds a non-match. Once the loop completes it ensures that all tlist
items were
On Wed, Oct 28, 2015 at 10:44:37AM +0300, Dmitry Voronin wrote:
> I have a database testdb with commet 'test comment' and security label
> 'classified'. I create dump by pg_dump:
>
> pg_dump -h 127.0.0.1 -d testdb -U postgres --format c dump
>
> So, I want to restore a dump with comment and secu
Jim Nasby writes:
> On 10/28/15 5:14 PM, Tom Lane wrote:
>> As of the end of this month, I will be departing Salesforce.com and
>> joining Crunchy Data Solutions (http://crunchydatasolutions.com),
> So I guess this means that the Fedora-wearing Elephant that ended up on
> a Cloud[1] is suddenly
On 10/28/15 5:14 PM, Tom Lane wrote:
As of the end of this month, I will be departing Salesforce.com and
joining Crunchy Data Solutions (http://crunchydatasolutions.com),
whom you might recognize as being already the employers of Stephen
Frost, Joe Conway, and Greg Smith, as well as a few other f
Hi,
Was reviewing recent commits, and it seems the following commit adds an
extra line to some comments. Just wanted to cross-check if that was
intentional.
Commit: http://goo.gl/zxA00l
Pre-Commit: http://goo.gl/2DpLxi
Post-Commit: http://goo.gl/eKcNm3
Apologies for the noise, if this was intent
On 10/28/15 11:52 PM, Robert Haas wrote:
-0 on this concept from me. I'm not going to vigorously oppose it, but:
1. You can always do it in the query if you really want it.
True, but not always practical.
2. If you're the sort of person liable to be confused by t/f, you
probably aren't in t
On 2015-10-28 23:38:45 +, Greg Stark wrote:
> On Wed, Oct 28, 2015 at 10:52 PM, Robert Haas wrote:
> > 3. I really don't want to end up with a bunch of features of this type
> > for a variety of different data types.
>
> We already have \pset null which feels very similar.
It's data type neu
On Wed, Oct 28, 2015 at 10:52 PM, Robert Haas wrote:
> 3. I really don't want to end up with a bunch of features of this type
> for a variety of different data types.
We already have \pset null which feels very similar. It's not like 'f'
and 't' are terribly common and probably different from how
On Wed, Oct 28, 2015 at 10:03 AM, Marko Tiikkaja wrote:
> Hello hello,
>
> Since the default t/f output for booleans is not very user friendly,
> attached is a patch which enables you to do for example the following:
>
> =# \pset true TRUE
> Boolean TRUE display is "TRUE".
> =# \pset false FALSE
>
On 28 October 2015 at 22:14, Tom Lane wrote:
> As of the end of this month, I will be departing Salesforce.com and
> joining Crunchy Data Solutions (http://crunchydatasolutions.com),
> whom you might recognize as being already the employers of Stephen
> Frost, Joe Conway, and Greg Smith, as well a
As of the end of this month, I will be departing Salesforce.com and
joining Crunchy Data Solutions (http://crunchydatasolutions.com),
whom you might recognize as being already the employers of Stephen
Frost, Joe Conway, and Greg Smith, as well as a few other folk who
hang out on pghackers.
While I
Can anyone identify a likely cause of the stack traces reported here:
https://retrace.fedoraproject.org/faf/reports/853674/
Apparently, what's happening is that PGSemaphoreUnlock is hitting
elog(FATAL, "semop(id=%d) failed: %m", sema->semId);
and then that's being promoted to a PANIC, p
On 10/28/2015 01:58 PM, Peter Eisentraut wrote:
> On 10/28/15 10:27 AM, Bill Moran wrote:
>> See subject. Aside from them being divvied up by datatype, they seem
>> to be ordered randomly. Since I'm putting together a patch that will
>> add some GUCs, do I just add them to the end of the list?
>
>
On Wed, 28 Oct 2015 16:58:30 -0400
Peter Eisentraut wrote:
> On 10/28/15 10:27 AM, Bill Moran wrote:
> > See subject. Aside from them being divvied up by datatype, they seem
> > to be ordered randomly. Since I'm putting together a patch that will
> > add some GUCs, do I just add them to the end o
On 10/28/15 10:27 AM, Bill Moran wrote:
> See subject. Aside from them being divvied up by datatype, they seem
> to be ordered randomly. Since I'm putting together a patch that will
> add some GUCs, do I just add them to the end of the list?
The initial commit grouped them logically, and it went d
Robert Haas wrote:
> Another point I want to reiterate - because nobody seems to be
> addressing it - is that some of these messages are totally useless. I
> grant that printing the transaction state (XIDs, CIDs, etc.) is
> useful. But does anybody really think that it's useful for every
> state
Thanks for clarifying my doubt...
--
Muthiah Rajan
On Wed, Oct 28, 2015 at 6:19 PM, Kevin Grittner wrote:
> On Tuesday, October 27, 2015 10:57 PM, Muthiah Rajan
> wrote:
> > On 27-Oct-2015 7:37 PM, "Kevin Grittner" wrote:
>
> >> It is more problematic where a shop wants to use serializable
>
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
Hi friends,
I'm Fabio Mendonça (Brazil) and I initiated a work with PostgreSQL, I work with
Oracle , DB2 , Sybase and Informix , but PostgreSQL is a sweet experience.
In this moment I'm looking any help, because the articles that I've found not
solve the problem.
The Cenario:
I 've a proc
2015-10-28 18:38 GMT+01:00 Tom Lane :
> 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
> > better
Jeff Janes writes:
> On Tue, Sep 29, 2015 at 7:53 AM, Robbie Harwood wrote:
>> Robbie Harwood writes:
>>
>> Michael Paquier writes:
>>
>>> Well, the issue is still here: login through gssapi fails with
>>> your patch, not with HEAD. This patch is next on my review list by
>
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
> better to offer. (Corey called it "only", but that d
2015-10-28 18:03 GMT+01:00 Marko Tiikkaja :
> On 10/28/15 5:53 PM, Pavel Stehule wrote:
>
>> what is use case for this function and why it should be in core?
>>
>
> Corey had one example in his email, but I can offer another one which came
> up this week at $work. The query looked something like
On Wed, Oct 28, 2015 at 5:26 PM, Jeff Janes wrote:
> I figured it would go something like this:
>
> DEBUG1 once or a few times per statement/autovac/checkpoint
> DEBUG2 several times per statement/autovac/checkpoint (like once per
> joined relation in the planner)
> DEBUG3 once or a few times per
On 10/28/15 5:53 PM, Pavel Stehule wrote:
what is use case for this function and why it should be in core?
Corey had one example in his email, but I can offer another one which
came up this week at $work. The query looked something like this:
SELECT a, sum(amount), onlyvalue(rolling_count)
2015-10-28 17:50 GMT+01:00 Marko Tiikkaja :
> Hi,
>
> 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 better
> to offer. (Corey ca
Hi,
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
better to offer. (Corey called it "only", but that doesn't really work
since
On Tue, Sep 29, 2015 at 7:53 AM, Robbie Harwood wrote:
> Robbie Harwood writes:
>
> Michael Paquier writes:
>
>> Well, the issue is still here: login through gssapi fails with
>> your patch, not with HEAD. This patch is next on my review list by
>> the way so I'll see what I
On Wed, Oct 28, 2015 at 6:57 AM, Robert Haas wrote:
> On Wed, Oct 28, 2015 at 1:51 AM, Tom Lane wrote:
>> Craig Ringer writes:
>>> I think it'd be helpful to define some level of policy about what the
>>> debug levels are intended for, so there's some guidance on what level
>>> to emit messages
On 27 October 2015 at 20:51, Tom Lane wrote:
>
> Craig Ringer writes:
> > I think it'd be helpful to define some level of policy about what the
> > debug levels are intended for, so there's some guidance on what level
> > to emit messages on rather than playing "pick a number".
>
> +1 ... I doubt
Andres Freund writes:
> On 2015-10-28 11:42:28 -0400, Tom Lane wrote:
>> 1. Invent a "--with-werror" configure switch that causes -Werror to be
>> added to the CFLAGS, but not while running tests that it'd break.
>>
>> 2. Explicitly filter -Werror out of the user-provided CFLAGS while running
>>
On Sat, Oct 17, 2015 at 1:48 AM, Michael Paquier wrote:
> On Sat, Oct 17, 2015 at 5:15 AM, Nikolay Shaplov wrote:
>> Or it's ready to commit, and just not marked this way?
>
> No, I don't think we have reached this state yet.
>
>> I am going to make report based on this patch in Vienna. It would be
On 2015-10-28 11:42:28 -0400, Tom Lane wrote:
> In view of your point (1), I'd be okay with inventing an EXTRA_CFLAGS
> argument that is added to, rather than replacing, the automatically
> computed flags. But I think that configure must include such flags
> for its own compile runs, else it is no
Andres Freund writes:
> On 2015-10-28 09:36:39 -0400, Tom Lane wrote:
>> Andres Freund writes:
>>> 1) ./configure CFLAGS=... essentially breaks --enable-debug and related
>>> options, overwrites -O2 as the default and such. That's imo pretty
>>> confusing.
>>> 2) I like to be able to pass -Werror
Valery Popov writes:
> 28.10.2015 16:33, Tom Lane ïèøåò:
>> The standard way of dealing with that is to include logic in the query to
>> limit the recursion depth, for example ...
> Yes, I agree with this thesis. But I think in some cases would be
> better to receive error message and stop exec
28.10.2015 16:33, Tom Lane пишет:
Valery Popov writes:
Recursive queries are typically used to deal with hierarchical or
tree-structured data.
In some conditions when data contain relationships with cycles recursive query
will loop
unlimited and significantly slows the client's session.
Th
At PGconf.EU, I could have a talk with Robert about this topic,
then it became clear we have same idea.
> ++
> |sub-plan | * Sub-Plan 1 ... Index Scan on p1
> |index on *-> * Sub-Plan 2 ... PartialSeqScan on p2
> |shared | * Sub-Plan 2 ... PartialSeqScan on p2
> |memory
Pavel Stehule writes:
> 2015-10-28 14:33 GMT+01:00 Tom Lane :
>> Also, there are already ways to constrain queries-gone-crazy; particularly
>> statement_timeout, which has the advantage that it works for other types
>> of badly-written queries not only this one.
> isn't the recursive limits much
2015-10-28 14:33 GMT+01:00 Tom Lane :
> Valery Popov writes:
> > Recursive queries are typically used to deal with hierarchical or
> > tree-structured data.
> > In some conditions when data contain relationships with cycles
> recursive query will loop
> > unlimited and significantly slows the cl
See subject. Aside from them being divvied up by datatype, they seem
to be ordered randomly. Since I'm putting together a patch that will
add some GUCs, do I just add them to the end of the list?
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chang
On 2015-10-28 09:36:39 -0400, Tom Lane wrote:
> Andres Freund writes:
> > I rather regularly want to pass extra flags to configure without
> > overwriting CFLAGS. There's two basic reasons:
>
> > 1) ./configure CFLAGS=... essentially breaks --enable-debug and related
> >options, overwrites -O
On Sun, Oct 18, 2015 at 12:17 AM, Robert Haas wrote:
>> So reviewing patch 13 isn't possible without prior knowledge.
>
> The basic question for patch 13 is whether ephemeral record types can
> occur in executor tuples in any contexts that I haven't identified. I
> know that a tuple table slot ca
On Wed, Oct 28, 2015 at 1:51 AM, Tom Lane wrote:
> Craig Ringer writes:
>> I think it'd be helpful to define some level of policy about what the
>> debug levels are intended for, so there's some guidance on what level
>> to emit messages on rather than playing "pick a number".
>
> +1 ... I doubt
On Wed, Oct 28, 2015 at 02:42:19PM +0100, Robert Haas wrote:
> On Wed, Oct 28, 2015 at 2:17 PM, Andres Freund wrote:
> >> I use COPT for this purpose.
> >
> > Unless I miss something you can't just pass that to configure though,
> > right? I.e. it has to be passed to each make invocation?
>
> Wha
On Wed, Oct 28, 2015 at 2:17 PM, Andres Freund wrote:
>> I use COPT for this purpose.
>
> Unless I miss something you can't just pass that to configure though,
> right? I.e. it has to be passed to each make invocation?
What I do is:
echo COPT=-Wall -Werror > src/Makefile.custom
--
Robert Haas
Andres Freund writes:
> I rather regularly want to pass extra flags to configure without
> overwriting CFLAGS. There's two basic reasons:
> 1) ./configure CFLAGS=... essentially breaks --enable-debug and related
>options, overwrites -O2 as the default and such. That's imo pretty
>confusin
Valery Popov writes:
> Recursive queries are typically used to deal with hierarchical or
> tree-structured data.
> In some conditions when data contain relationships with cycles recursive
> query will loop
> unlimited and significantly slows the client's session.
The standard way of dealing wit
On 2015-10-28 12:20:22 +0100, Robert Haas wrote:
> On Wed, Oct 28, 2015 at 11:55 AM, Andres Freund wrote:
> > I rather regularly want to pass extra flags to configure without
> > overwriting CFLAGS. There's two basic reasons:
> >
> > 1) ./configure CFLAGS=... essentially breaks --enable-debug and
On Tuesday, October 27, 2015 10:57 PM, Muthiah Rajan wrote:
> On 27-Oct-2015 7:37 PM, "Kevin Grittner" wrote:
>> It is more problematic where a shop wants to use serializable
>> transactions to ensure data integrity.
> This may be a trivial thing But what do you mean by shops? I
> actually
On Sun, Oct 25, 2015 at 7:12 PM, Tomas Vondra
wrote:
>> By default, or when uniform is specified, all values in the range are
>> drawn with equal probability. Specifying gaussian or exponential
>> options modifies this behavior; each requires a mandatory threshold
>> which determines the precise s
On Mon, Oct 26, 2015 at 3:12 AM, Amit Langote
wrote:
> On 2015/10/23 19:02, Amit Langote wrote:
>> On 2015/10/23 18:51, Etsuro Fujita wrote:
>>>
>>> This is really really nitpicking, but I noticed that there is an implicit
>>> rule concerning the message format in ATWrongRelkindError; if more than
On Wed, Oct 28, 2015 at 11:55 AM, Andres Freund wrote:
> I rather regularly want to pass extra flags to configure without
> overwriting CFLAGS. There's two basic reasons:
>
> 1) ./configure CFLAGS=... essentially breaks --enable-debug and related
>options, overwrites -O2 as the default and suc
On Fri, Oct 23, 2015 at 11:51 AM, Etsuro Fujita
wrote:
> BTW, I found an incorrect error message in ATWrongRelkindError. Attached is
> a patch for fixing the message.
Committed and back-patched to 9.3.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi,
I rather regularly want to pass extra flags to configure without
overwriting CFLAGS. There's two basic reasons:
1) ./configure CFLAGS=... essentially breaks --enable-debug and related
options, overwrites -O2 as the default and such. That's imo pretty
confusing.
2) I like to be able to p
Hello hello,
Since the default t/f output for booleans is not very user friendly,
attached is a patch which enables you to do for example the following:
=# \pset true TRUE
Boolean TRUE display is "TRUE".
=# \pset false FALSE
Boolean FALSE display is "FALSE".
=# select true, false;
bool | boo
On Mon, 26 Oct 2015 16:25:57 -0400
Peter Eisentraut wrote:
> Also, this assumes that all the components other than host and port
> are the same. Earlier there was a discussion about why the ports
> would ever need to be different. Well, why can't the database names
> be different? I could have
2015-10-28 8:33 GMT+01:00 Valery Popov :
> Hi, Hackers
>
> Recursive queries are typically used to deal with hierarchical or
> tree-structured data.
> In some conditions when data contain relationships with cycles recursive
> query will loop
> unlimited and significantly slows the client's sessio
Hello, guys.
I have a database testdb with commet 'test comment' and security label
'classified'. I create dump by pg_dump:
pg_dump -h 127.0.0.1 -d testdb -U postgres --format c dump
So, I want to restore a dump with comment and security label to testdb_restore.
I run:
pg_restore -h 127.0.0.1
Hi, Hackers
Recursive queries are typically used to deal with hierarchical or
tree-structured data.
In some conditions when data contain relationships with cycles recursive query
will loop
unlimited and significantly slows the client's session.
To prevent "infinite" loop I suggest the max_recur
Thanks Amit... :-)
--
View this message in context:
http://postgresql.nabble.com/Disabling-START-TRANSACTION-for-a-SuperUser-tp5871630p5871739.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
64 matches
Mail list logo