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 improves
2013/8/4 Erik Rijkers e...@xs4all.nl:
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
Thom Brown t...@linux.com 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
2013/8/4 Ian Lawrence Barwick barw...@gmail.com:
2013/8/4 Erik Rijkers e...@xs4all.nl:
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
Alvaro Herrera alvhe...@2ndquadrant.com 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
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
On Sun, Aug 4, 2013 at 6:20 PM, Tom Lane t...@sss.pgh.pa.us 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
On Mon, Jul 29, 2013 at 1:42 AM, Andrew Gierth
and...@tao11.riddles.org.uk 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
On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
rler...@cisco.com 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
On 2013-08-04 20:33:50 -0400, Robert Haas wrote:
On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
rler...@cisco.com wrote:
Hi. Has anyone had experience building PostgreSQL to support Address Space
Layout Randomization (ASLR)? I recently took a brute-force approach
(compiling
Robert Haas robertmh...@gmail.com writes:
On Sun, Aug 4, 2013 at 6:20 PM, Tom Lane t...@sss.pgh.pa.us 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
On Sun, Aug 4, 2013 at 8:54 PM, Andres Freund and...@2ndquadrant.com 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
On 2013-08-04 21:07:02 -0400, Robert Haas wrote:
On Sun, Aug 4, 2013 at 8:54 PM, Andres Freund and...@2ndquadrant.com 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
Robert Haas robertmh...@gmail.com writes:
On Wed, Jul 31, 2013 at 4:35 PM, Robert Lerche (rlerche)
rler...@cisco.com wrote:
Hi. Has anyone had experience building PostgreSQL to support Address Space
Layout Randomization (ASLR)? I recently took a brute-force approach
(compiling everything
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 this
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, there's
On Fri, 2 Aug 2013 08:16:15 -0400
Robert Haas robertmh...@gmail.com wrote:
On Tue, Jul 30, 2013 at 3:10 AM, Gibheer gibh...@zero-knowledge.org
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
17 matches
Mail list logo