Tom Lane t...@sss.pgh.pa.us writes:
On Apr 2, 2012, at 11:24 AM, Peter Eisentraut wrote:
Or an extension could specify itself which version numbering scheme it
uses. This just has to be a reference to a type, which in turn could be
semver, debversion, or even just numeric or text (well, maybe
On Sat, Mar 31, 2012 at 5:34 PM, Peter Geoghegan pe...@2ndquadrant.com wrote:
Since any backend write is necessarily the result of that backend
trying to allocate a buffer, I think maybe we should just count
whether the number of times it was trying to allocate a buffer *using
a BAS* vs. the
On Sun, Apr 1, 2012 at 7:22 AM, Dimitri Fontaine dimi...@2ndquadrant.fr wrote:
See above example: I am pretty sure you need a stack.
In next version, certainly. As of now I'm willing to start a new stack
in each command executed in a command trigger. That means 9.2 will only
expose the first
Hi Gabriele,
Le 31/03/2012 14:25, Gabriele Bartolini a écrit :
Hi Gilles,
first and foremost, sorry for jumping in this thread so late. I
read all previous discussions and I'd be happy to help you with this
patch.
Agreed and sorry for the response delay. I've attached 2 patches
here,
On Mon, Apr 2, 2012 at 5:23 AM, Dave Page dp...@pgadmin.org wrote:
If homebrew intentionally creates a hole like that, then for as long
as I'm one of the PostgreSQL webmasters it will *never* be listed on
our download pages.
I think that's a bit harsh. It's not as if the PostgreSQL package
Robert Haas wrote:
Kevin Grittner wrote:
I can't help thinking that the background hinter I had ideas
about writing would prevent many of the reads of old CLOG pages,
taking a lot of pressure off of this area. It just occurred to me
that the difference between that idea and having an
Robert Haas robertmh...@gmail.com writes:
I think we're talking past each other. If someone executes DDL
command A and the command trigger executes DDL command B which fires
another command trigger, then the command trigger for A needs to see
the information relevant to A both before and
I haven't finished reviewing this yet - but there are some things that
need to be fixed.
First, either the creation of the destination directory needs to be
delayed until all the sanity checks have passed and we're sure we're
actually going to write something there, or it needs to be removed
Shigeru HANADA wrote:
Attached are latest version of pgsql_fdw patches. Note that
pgsql_fdw_analyze.patch is only for test the effect of local
statistics.
Please apply patches in the order below:
(1) pgsql_fdw_v18.patch
(2) pgsql_fdw_pushdown_v11.patch
(3) pgsql_fdw_analyze.patch (if you
On Sun, Apr 1, 2012 at 12:35 PM, Joachim Wieland j...@mcknight.de wrote:
On Wed, Mar 28, 2012 at 2:20 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
My main comment about the current patch is that it looks like it's
touching pg_restore parallel code by moving some stuff into parallel.c.
On Tue, Apr 3, 2012 at 9:34 AM, Robert Haas robertmh...@gmail.com wrote:
On Sun, Apr 1, 2012 at 12:35 PM, Joachim Wieland j...@mcknight.de wrote:
Unfortunately this is not really the case. What is being moved out of
pg_backup_archiver.c and into parallel.c is either the shutdown logic
that has
Excerpts from Joachim Wieland's message of mar abr 03 11:40:31 -0300 2012:
On Tue, Apr 3, 2012 at 9:34 AM, Robert Haas robertmh...@gmail.com wrote:
Hmm. It looks to me like the part-two patch still contains a bunch of
code rearrangement. For example, the current code for
On Tue, Apr 3, 2012 at 10:40 AM, Joachim Wieland j...@mcknight.de wrote:
On a similar note, what's the point of changing struct Archive to have
int numWorkers instead of int number_of_jobs, and furthermore
shuffling the declaration around to a different part of the struct?
number_of_jobs was
If you use ALTER ROLE/DATABASE SET to configure an invalid
search_path, PostgreSQL 9.1 issues a complaint about the invalid
setting on each new connection. This is a behavior change relatively
to previous releases, which did not. git bisect blames this commit:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 10:40 AM, Joachim Wieland j...@mcknight.de wrote:
I completely agree. Assertions helped a lot dealing with concurrent
code. How do you want to tackle this for now? Want me to create a
separate header pg_assert.h as part of my
Robert Haas robertmh...@gmail.com writes:
If you use ALTER ROLE/DATABASE SET to configure an invalid
search_path, PostgreSQL 9.1 issues a complaint about the invalid
setting on each new connection. This is a behavior change relatively
to previous releases, which did not.
I would say that's
On Tue, Apr 3, 2012 at 11:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 10:40 AM, Joachim Wieland j...@mcknight.de wrote:
I completely agree. Assertions helped a lot dealing with concurrent
code. How do you want to tackle this for
On Tue, Apr 3, 2012 at 8:22 AM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Apr 2, 2012 at 5:23 AM, Dave Page dp...@pgadmin.org wrote:
If homebrew intentionally creates a hole like that, then for as long
as I'm one of the PostgreSQL webmasters it will *never* be listed on
our download
Excerpts from Tom Lane's message of mar abr 03 12:38:20 -0300 2012:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 10:40 AM, Joachim Wieland j...@mcknight.de wrote:
I completely agree. Assertions helped a lot dealing with concurrent
code. How do you want to tackle this
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 11:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Possibly we could move assert.c into src/port/ and make it part of
libpgport?
The trouble is that it calls write_stderr(), which has a non-trivial
implementation on Windows that I
On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
If you use ALTER ROLE/DATABASE SET to configure an invalid
search_path, PostgreSQL 9.1 issues a complaint about the invalid
setting on each new connection. This is a behavior change
On Tue, Apr 3, 2012 at 11:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 11:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Possibly we could move assert.c into src/port/ and make it part of
libpgport?
The trouble is that it calls
Alvaro Herrera alvhe...@commandprompt.com writes:
That only leaves assert_enabled to be handled. In the backend it lives
in guc.c; what to do about frontend code?
There's no mechanism for turning such a switch on or off in most
frontend code anyway. I'd think it could just be assumed to be on
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 11:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Well, if we don't have a solution to that problem then it's premature
to propose making Assert available to frontend code. So my opinion
is that that idea is too half-baked to be
On Tue, Apr 3, 2012 at 11:56 AM, Christopher Browne cbbro...@gmail.com wrote:
It's pretty typical for MacOS applications to require enter your
password; I need to su to root to install this! in plenty of places
where the UI does not actually tell you what is being done as root.
After enough
On Tue, Apr 3, 2012 at 12:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 11:59 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Well, if we don't have a solution to that problem then it's premature
to propose making Assert available to frontend
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 12:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
No, the reason for write_stderr() is that fprintf(stderr) is unreliable
on Windows. If memory serves, it can actually crash in some situations.
Dude, we're already doing
On Tue, Apr 3, 2012 at 12:37 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 12:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
No, the reason for write_stderr() is that fprintf(stderr) is unreliable
on Windows. If memory serves, it can
On Tue, Apr 3, 2012 at 12:05 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
If you use ALTER ROLE/DATABASE SET to configure an invalid
search_path, PostgreSQL 9.1 issues a complaint
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 12:05 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I would say that's an improvement. Do you think it isn't?
It seems like a log spam hazard at high connection
On 3 April 2012 19:16, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 12:05 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I would say that's an improvement. Do you think it
On Sun, Apr 01, 2012 at 07:23:06PM -0400, Tom Lane wrote:
Marko Kreen mark...@gmail.com writes:
So the proper approach would be to have new API call, designed to
handle it, and allow early-exit only from there.
That would also avoid any breakage of old APIs. Also it would avoid
any
On Tue, Apr 3, 2012 at 2:16 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Apr 3, 2012 at 12:05 PM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Apr 3, 2012 at 11:49 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I would say that's an improvement. Do you
Robert Haas wrote:
On Mon, Apr 2, 2012 at 5:23 AM, Dave Pagedp...@pgadmin.org wrote:
If homebrew intentionally creates a hole like that, then for as long
as I'm one of the PostgreSQL webmasters it will *never* be listed on
our download pages.
I think that's a bit harsh. It's not as if the
On 04/02/2012 01:03 PM, Tom Lane wrote:
Andrew Dunstanand...@dunslane.net writes:
On 04/02/2012 12:44 PM, Tom Lane wrote:
You could do something like having a list of pending chunks for each
value of (pid mod 256). The length of each such list ought to be plenty
short under ordinary
Marko Kreen mark...@gmail.com writes:
The fact remains that upper-level code must cooperate with callback.
Why is it useful to hijack PQgetResult() to do so?
Because that's the defined communications channel. We're not
hijacking it. If we're going to start using pejorative words here,
I will
Robert Haas robertmh...@gmail.com writes:
So we have an established precedent that it is right to warn about
things that are sketchy at the time that they are defined, but not
every time they are used.
Sure, but we don't have that option available to us here --- or more
accurately, ALTER
On Tue, Apr 03, 2012 at 05:32:25PM -0400, Tom Lane wrote:
Marko Kreen mark...@gmail.com writes:
The fact remains that upper-level code must cooperate with callback.
Why is it useful to hijack PQgetResult() to do so?
Because that's the defined communications channel. We're not
hijacking
While I was doing this I always thought this would have been a better
approach for my previous project, an accounting application. If I could
just have stored entities like invoice customer as a single document that
is inserted, updated, etc. atomically it would be a lot simpler and faster
On 04/01/2012 04:19 PM, Jay Levitt wrote:
POSSIBLE OBJECTIONS/PREREQUISITES
10. There is no homebrew support for multiple versions, and no current
plans to add it (though it's on the wishlist). This means homebrew is
only useful if I want to install a PostgreSQL thingie is the common
Mac use
On 4/3/12 5:22 AM, Robert Haas wrote:
On Mon, Apr 2, 2012 at 5:23 AM, Dave Page dp...@pgadmin.org wrote:
If homebrew intentionally creates a hole like that, then for as long
as I'm one of the PostgreSQL webmasters it will *never* be listed on
our download pages.
I don't agree. Listed with a
On Tue, Apr 3, 2012 at 7:48 PM, Josh Berkus j...@agliodbs.com wrote:
On 4/3/12 5:22 AM, Robert Haas wrote:
On Mon, Apr 2, 2012 at 5:23 AM, Dave Page dp...@pgadmin.org wrote:
If homebrew intentionally creates a hole like that, then for as long
as I'm one of the PostgreSQL webmasters it will
On Tue, Apr 3, 2012 at 6:58 PM, Greg Smith g...@2ndquadrant.com wrote:
--Documentation
Homebrew will have to become more complicated if it's going to try and
wander down this path. With complexity and backward compatibility come
increased needs for documentation.
One more to add:
--QA
On Tue, Apr 3, 2012 at 2:37 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
So we have an established precedent that it is right to warn about
things that are sketchy at the time that they are defined, but not
every time they are used.
Sure, but we don't
On Wed, Apr 4, 2012 at 1:19 AM, Dave Page dp...@pgadmin.org wrote:
then, we're talking about making parts of the filesystem
world-writeable so it doesn't even matter if the user is running as an
admin for a trojan or some other nasty to attack the system.
The argument is that a trojan or other
On 03/05/2012 05:20 PM, Tomas Vondra wrote:
What is the current state of this effort? Is there someone else working
on that? If not, I propose this (for starters):
* add a new page Performance results to the menu, with a list of
members that uploaded the perfomance-results
* for
On 03/25/2012 04:29 PM, Jim Nasby wrote:
Another $0.02: I don't recall the community using pg_bench much at all
to measure latency... I believe it's something fairly new. I point
this out because I believe there are differences in analysis that you
need to do for TPS vs latency. I think
Hi all,
I noticed psql's tab-completion for 'WITH' is a bit overeager. If you
try to tab-complete commands like:
ALTER ROLE jsmith WITH [TAB]
COPY tbl FROM 'filename' WITH [TAB]
you'll get 'RECURSIVE' unhelpfully filled in. I think 'RECURSIVE'
should only be suggested if 'WITH' is the first
For a C implementation, it could interesting to consider LZ4 algorithm, since
it is written natively in this language. In contrast, Snappy has been ported
to C by Andy from the original C++ Google code, which lso translate into
less extensive usage and tests.
http://code.google.com/p/lz4/
Dear Postgresql hackers,
We are organizing a micro-conference on scaling both upwards (many
cores) and downwards (low footprint, energy efficiency) that targets
all layers of the software stack. Our intent is to bring together
application, libraries and kernel developers to discuss the
50 matches
Mail list logo
