On 10 May 2013 23:41, Jeff Davis pg...@j-davis.com wrote:
On Fri, 2013-05-10 at 18:32 +0100, Simon Riggs wrote:
We don't write() WAL except with an immediate sync(), so the chances
of what you say happening are very low to impossible.
Are you sure? An XLogwrtRqst contains a write and a flush
On Thu, May 9, 2013 at 7:36 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
Some of this is getting solved by making PostgreSQL more pluggable in
ways that isolate the proprietary stuff, i.e. make people not have to
touch the PostgreSQL core code much, if at all, in order to provide
Simpler version of 'pgbench --throttle' by handling throttling at the
beginning of the transaction instead of doing it at the end.
This is for reference to the next commitfest.
--
Fabien.diff --git a/contrib/pgbench/pgbench.c b/contrib/pgbench/pgbench.c
index bc01f07..13b33c7 100644
---
On Sat, May 11, 2013 at 11:17:03AM -0400, Robert Haas wrote:
On Thu, May 9, 2013 at 7:36 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
Some of this is getting solved by making PostgreSQL more pluggable in
ways that isolate the proprietary stuff, i.e. make people not have to
touch
On Fri, May 10, 2013 at 9:50 AM, Peter Eisentraut pete...@gmx.net wrote:
On 8/9/12 9:08 AM, Robert Haas wrote:
On Wed, Aug 8, 2012 at 6:50 PM, David Fetter da...@fetter.org wrote:
I'm wondering if perhaps -- in addition to what you've done here -- we
should make psql -1 error out if reading
David Fetter da...@fetter.org writes:
On Sat, May 11, 2013 at 11:17:03AM -0400, Robert Haas wrote:
Some kind of extendable parser would be awesome. It would need to tie
into the rewriter also.
No, I don't have a clue what the design looks like.
That's a direction several of the
On Wed, May 8, 2013 at 1:48 PM, Jim Nasby j...@nasby.net wrote:
On 5/8/13 3:54 AM, Heikki Linnakangas wrote:
On 24.04.2013 14:31, Florian Pflug wrote:
On Apr23, 2013, at 23:25 , Alexander Korotkovaekorot...@gmail.com
wrote:
I've taken a brief look on the paper and implementation. As I can
On Fri, May 10, 2013 at 08:03:38PM -0400, Bruce Momjian wrote:
On Fri, May 10, 2013 at 12:36:21PM -0400, Evan D. Hoffman wrote:
pg.dropped.16 INTEGER /* dummy */,
pg.dropped.17 INTEGER /* dummy */,
pg.dropped.18 INTEGER /* dummy
On Sat, May 11, 2013 at 12:27 PM, Tom Lane t...@sss.pgh.pa.us wrote:
By the time you've got an expression tree, the problem is mostly solved,
at least so far as parser extension is concerned.
Right.
More years ago than I care to admit, I worked on systems that had
run-time-extensible parsers
