On Thu, Jun 12, 2014 at 9:31 AM, Gurjeet Singh gurj...@singh.im wrote:
I don't have intimate knowledge of recovery but I think the above
assessment of recovery's operations holds true. If you still think
this is a concern, can you please provide a bit firm example using
which I can visualize
I would suggest to add that to https://wiki.postgresql.org/wiki/Todo.
I may look into it when I have time, over the summer. The key point is
that there is no need for a temporary installation, but only of a
temporary cluster, and to trick this cluster into loading the
uninstalled extension,
Re: Amit Kapila 2014-06-13
CAA4eK1KLn1SmgVtd=5emabqxrrpveedtbuu94e-repmwxwv...@mail.gmail.com
Agreed, I had mentioned in Notes section of document. Apart from that
I had disallowed parameters that are excluded from postgresql.conf by
initdb (Developer options) and they are recommended in user
On Sat, Jun 14, 2014 at 04:56:44PM -0700, Kevin Grittner wrote:
Attached is a WIP patch for implementing the capture of delta
relations for a DML statement, in the form of two tuplestores --
one for the old versions and one for the new versions.
Thanks!
Any chance we might be able to surface
David Fetter da...@fetter.org wrote:
Any chance we might be able to surface the old version for the
case of UPDATE ... RETURNING?
Not as part of this patch.
Of course, once delta relations are available, who knows what
people might do with them. I have a hard time imagining exactly
how you
On Jun 15, 2014, at 12:25 AM, Fabien COELHO coe...@cri.ensmp.fr wrote:
I'm not sure the extension is sought for in the cluster (ie the database data
directory). If you do make install the shared object is installed in some
/usr/lib/postgresql/... directory (under unix), and it is loaded from
On 06/10/2014 02:46 PM, David E. Wheeler wrote:
On Jun 10, 2014, at 12:06 PM, Oleg Bartunov obartu...@gmail.com wrote:
we have many other tasks than guessing the language name.
jsquery is just an extension, which we invent to test our indexing
stuff. Eventually, it grew out. I think we'll
On 06/15/2014 04:58 PM, Josh Berkus wrote:
I've been poking at the various json-query syntaxes you forwarded, and
none of them really work for the actual jsquery features. Also, the
existing syntax has the advantage of being *simple*, relatively
speaking, and reasonably similar to JSONPATH.
Hi! Here is my report for the last two weeks.Weeks 3 and 4 - 2014/06/15
During my third week, I haven't had time to work on GSoC a lot, because of
my exams and my relocation (that's why I didn't deem necessary to post a
report last Sunday). But last week has been much more productive, as I am
now
On Sun, Jun 15, 2014 at 6:29 PM, Christoph Berg c...@df7cb.de wrote:
Re: Amit Kapila 2014-06-13 CAA4eK1KLn1SmgVtd=
5emabqxrrpveedtbuu94e-repmwxwv...@mail.gmail.com
Agreed, I had mentioned in Notes section of document. Apart from that
I had disallowed parameters that are excluded from
On Sat, Jun 14, 2014 at 8:07 PM, Tom Lane t...@sss.pgh.pa.us wrote:
After giving somebody advice, for the Nth time, to install a
memory-consumption ulimit instead of leaving his database to the tender
mercies of the Linux OOM killer, it occurred to me to wonder why we don't
provide a built-in
* Tom Lane (t...@sss.pgh.pa.us) wrote:
Adam Brightwell adam.brightw...@crunchydatasolutions.com writes:
Through this effort, we have concluded that for RLS the case of
invalidating a plan is only necessary when switching between a superuser
and a non-superuser. Obviously, re-planning on
* Tom Lane (t...@sss.pgh.pa.us) wrote:
Craig Ringer cr...@2ndquadrant.com writes:
I agree, and now that the urgency of trying to deliver this for 9.4 is
over it's worth seeing if we can just run as table owner.
Failing that, we could take the approach a certain other RDBMS does and
make
On 06/16/2014 11:56 AM, Amit Kapila wrote:
On Sat, Jun 14, 2014 at 8:07 PM, Tom Lane t...@sss.pgh.pa.us
mailto:t...@sss.pgh.pa.us wrote:
After giving somebody advice, for the Nth time, to install a
memory-consumption ulimit instead of leaving his database to the tender
mercies of the Linux
On 06/13/2014 07:08 AM, Shreesha wrote:
I need to initialize the db as the root and start the database server
Assuming there's no way around doing this (it's generally not a good
idea), you can just use the simple program 'fakeroot'.
This program changes the return values from system calls via
On 05/30/2014 11:14 PM, Heikki Linnakangas wrote:
Yeah. To recap, the failure mode is that if the master crashes and
restarts, the transaction becomes visible in the master even though it
was never replicated.
Wouldn't another pg_clog bit for the transaction be able to sort that out?
--
Robert,
* Robert Haas (robertmh...@gmail.com) wrote:
On Wed, Jun 11, 2014 at 8:59 PM, Stephen Frost sfr...@snowman.net wrote:
In this case the user-defined code needs to return a boolean. We don't
currently do anything to prevent it from having side-effects, no, but
the same is true with
Kevin,
* Kevin Grittner (kgri...@ymail.com) wrote:
Robert Haas robertmh...@gmail.com wrote:
Even aside from security exposures, how
does a non-superuser who runs pg_dump know whether they've got a
complete backup or a filtered dump that's missing some rows?
This seems to me to be a
On Mon, May 26, 2014 at 6:23 AM, Ronan Dunklau ronan.dunk...@dalibo.com wrote:
Le dimanche 25 mai 2014 12:41:18 David Fetter a écrit :
On Fri, May 23, 2014 at 10:08:06PM +0200, Ronan Dunklau wrote:
Hello,
Since my last proposal didn't get any strong rebuttal, please find
attached a more
19 matches
Mail list logo
