> While we could complicate query_planner()'s API even more to add some
> understanding of unnecessary resjunk items, I think this is probably
> the straw that breaks the camel's back for the current approach here.
> There is already a comment like this in query_planner():
>
> * This introduce
Amit Kapila writes:
> On Saturday, August 03, 2013 12:53 AM Tom Lane wrote:
>> Yeah, this approach is a nonstarter because there's no reason to assume
>> that a postmaster started with default parameters will start
>> successfully,
>> or will be connectable-to if it does start. Maybe there's anot
Hello,
I am looking the effect of having large number of relation files under
$PGDATA/base/ (for example, in cases where I choose lower segment size
using --with-segsize). Consider a case where I am working with a large
database with large relations, for example a database similar in size
to what
> Robert Haas writes:
> > On Sun, Aug 4, 2013 at 6:20 PM, Tom Lane wrote:
> >> I think it's time to bite the bullet and *not* pass back completed paths.
> >> What's looking more attractive now is to just pass back the top-level
> >> RelOptInfo ("final_rel" in query_planner()).
>
> > I tend to th
On Saturday, August 03, 2013 12:53 AM Tom Lane wrote:
> Stephen Frost writes:
> > * Josh Berkus (j...@agliodbs.com) wrote:
> >> A much simpler solution to the issue Stephen proposes is to have a
> way
> >> to start up the server with all settings from ALTER SYSTEM SET
> disabled,
> >> just like so
On 2013-08-02 08:16:15 -0400, Robert Haas wrote:
> On Tue, Jul 30, 2013 at 3:10 AM, Gibheer wrote:
> > here is an update off my patch based on the discussion with Marko
> > Tiikkaja and Andres Freund.
> >
> > Marko and I had the idea of introducing reserved connections based on
> > roles as it wou
On Fri, 2 Aug 2013 08:16:15 -0400
Robert Haas wrote:
> On Tue, Jul 30, 2013 at 3:10 AM, Gibheer
> wrote:
> > here is an update off my patch based on the discussion with Marko
> > Tiikkaja and Andres Freund.
> >
> > Marko and I had the idea of introducing reserved connections based
> > on roles a
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Having said all that, there is one situation where this type of approach might
> still be useful even after such a fix, and that's KNNGist-style
> queries:
>
> select a,b,c from t order by col <-> constant limit 10;
>
> In a KNNGist search,
On Saturday, August 03, 2013 5:17 AM Josh Berkus wrote:
> Folks,
>
> The first CF for the 9.4 development cycle is officially over.
>
> In all, 49 patches were committed, 47 were returned with feedback, 6
> were rejected outright, and 6 were punted to CF2. We're 17 days over
> the CF deadline at
Robert Haas writes:
> On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
> wrote:
>> Hi. Has anyone had experience building PostgreSQL to support Address Space
>> Layout Randomization (ASLR)? I recently took a brute-force approach
>> (compiling everything with -fPIC and specifying -pie on
On 2013-08-04 21:07:02 -0400, Robert Haas wrote:
> On Sun, Aug 4, 2013 at 8:54 PM, Andres Freund wrote:
> >> AFAIK you've got it backwards: ASLR is something that happens
> >> automatically, unless you take steps to suppress it, at least on MacOS
> >> X. I not long ago built with EXEC_BACKEND on
On Sun, Aug 4, 2013 at 8:54 PM, Andres Freund wrote:
>> AFAIK you've got it backwards: ASLR is something that happens
>> automatically, unless you take steps to suppress it, at least on MacOS
>> X. I not long ago built with EXEC_BACKEND on that platform and found
>> that it broke stuff until I di
Robert Haas writes:
> On Sun, Aug 4, 2013 at 6:20 PM, Tom Lane wrote:
>> I think it's time to bite the bullet and *not* pass back completed paths.
>> What's looking more attractive now is to just pass back the top-level
>> RelOptInfo ("final_rel" in query_planner()).
> I tend to think this is a
On 2013-08-04 20:33:50 -0400, Robert Haas wrote:
> On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
> wrote:
> > Hi. Has anyone had experience building PostgreSQL to support Address Space
> > Layout Randomization (ASLR)? I recently took a brute-force approach
> > (compiling everything wi
On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
wrote:
> Hi. Has anyone had experience building PostgreSQL to support Address Space
> Layout Randomization (ASLR)? I recently took a brute-force approach
> (compiling everything with -fPIC and specifying -pie on all executables).
> This wo
On Mon, Jul 29, 2013 at 1:42 AM, Andrew Gierth
wrote:
> I propose the following patch (which goes on top of the current
> ordinality one) to implement the suggested grammar changes.
>
> I think this is the cleanest way, and I've tested that it both
> passes regression and allows constructs like WI
On Sun, Aug 4, 2013 at 6:20 PM, Tom Lane wrote:
> I've been looking at what it would take to do proper cost estimation
> for the recently-discussed patch to suppress calculation of unnecessary
> ORDER BY expressions. It turns out that knowledge of that would have
> to propagate into query_planner
I've been looking at what it would take to do proper cost estimation
for the recently-discussed patch to suppress calculation of unnecessary
ORDER BY expressions. It turns out that knowledge of that would have
to propagate into query_planner(), because the place where we do the cost
comparison bet
Alvaro Herrera writes:
> I remind you that event triggers are not fired for global objects
> such as databases and roles. Do you intend to lift that restriction?
That's not on my TODO list for 9.4. My understanding about implementing
that is:
- we agree that it would be nice to have,
- it r
2013/8/4 Ian Lawrence Barwick :
> 2013/8/4 Erik Rijkers :
>> On Sun, August 4, 2013 04:51, Ian Lawrence Barwick wrote:
>>> I just noticed that pg_restore executing in "verbose" mode displays the
>>> name of the object being restored, but not its schema.
>>>
>>
>> Good idea. We have many schemata w
Thom Brown writes:
> Could you please resubmit this without using SnapshotNow as it's no longer
> supported?
Sure, sorry that I missed that, please find v12 attached.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
templates.v12.patch.gz
De
2013/8/4 Erik Rijkers :
> On Sun, August 4, 2013 04:51, Ian Lawrence Barwick wrote:
>> I just noticed that pg_restore executing in "verbose" mode displays the
>> name of the object being restored, but not its schema.
>>
>
> Good idea. We have many schemata with tables of the same name and
> report
On Sun, August 4, 2013 04:51, Ian Lawrence Barwick wrote:
> I just noticed that pg_restore executing in "verbose" mode displays the
> name of the object being restored, but not its schema.
>
Good idea. We have many schemata with tables of the same name and
reporting the schema name certainly impr
23 matches
Mail list logo
