Hello,
I am new to postgresql code, I would like to start implementing easyish TODO
items. I have read most of the development guidelines, faqs, articles by
Greg Smith (Hacking Postgres with UDFs, Adding WHEN to triggers).
The item I would like to implement is adding CORRESPONDING [BY
On 18 September 2011 01:51, Greg Stark st...@mit.edu wrote:
I think we provided the qsort implementation for the benefit of
platforms that didn't have a decent one and then ended up switching to
use it always for some reason I don't recall. It wasn't because we
thought we were better at
On fre, 2011-09-16 at 07:38 -0500, Merlin Moncure wrote:
So, generally speaking, what kinds of things are going to be brought
up at the ISO meeting? Is this an opportunity to get postgres special
syntax drafted into the sql standard?
Don't expect to take a PostgreSQL-specific feature, say,
On fre, 2011-09-16 at 08:59 -0500, Dave Page wrote:
You're missing my point completely. You say you represent PostgreSQL
on the SQL Committee (or German working group, but that's not the
point), yet the PostgreSQL hackers didn't know that, and were making
other plans less than 2 years ago. For
On fre, 2011-09-16 at 10:57 -0400, Tom Lane wrote:
So it looks like it behooves us to cater for oom_score_adj in the
future. The simplest, least risky change that I can think of is to
copy-and-paste the relevant #ifdef code block in fork_process.c.
If we do that, then it would be up to the
On Sunday, September 18, 2011, Peter Eisentraut pete...@gmx.net wrote:
On fre, 2011-09-16 at 08:59 -0500, Dave Page wrote:
You're missing my point completely. You say you represent PostgreSQL
on the SQL Committee (or German working group, but that's not the
point), yet the PostgreSQL hackers
Susanne Ebrecht wrote:
Since 4 years I am PostgreSQL representative in SQL Standard
committee.
I wasn't aware of that. Thanks for taking the time to look out for
community interests.
The next ISO meeting will be soon - and of course there are lots of
drafts that needs decisions.
As
On sön, 2011-09-18 at 09:45 -0500, Dave Page wrote:
That is much more reasonable, though unfortunately not what was said.
Regardless, I stand by my main point that such a representative should
be communicating with the project regularly. Having a rep who works
outside the project is of no use
The 2nd CommitFest for 9.2 is in progress. It is scheduled to run
from September 15th (three days ago) until October 15th (just under
four weeks from now). No new patches should be added to it
(although, obviously, new versions of patches already in the CF are
expected).
Although this is just
On Tue, September 13, 2011 10:41, Jeff Davis wrote:
Another updated patch is attached.
Hi,
Below are 2 changes. The first change is an elog saying 'lower' instead of
'upper'.
The second change is less straightforward, but I think it should be changed too:
Rangetypes as it stands uses NULL
Peter Eisentraut pete...@gmx.net writes:
On fre, 2011-09-16 at 10:57 -0400, Tom Lane wrote:
So it looks like it behooves us to cater for oom_score_adj in the
future. The simplest, least risky change that I can think of is to
copy-and-paste the relevant #ifdef code block in fork_process.c.
If
Peter Eisentraut pete...@gmx.net writes:
On sön, 2011-09-18 at 09:45 -0500, Dave Page wrote:
That is much more reasonable, though unfortunately not what was said.
Regardless, I stand by my main point that such a representative should
be communicating with the project regularly. Having a rep
Hi,
I tried to apply the Grouping Sets Patch to 8.4, but received several Hunks
failed messages, does anyone know if the failing hunks can be applied
manually? Or what version they were applied to specifically?
--
Regards
David
On Mon, Sep 12, 2011 at 00:22, Tom Lane t...@sss.pgh.pa.us wrote:
The other thing that is going to be an issue is that I'm fairly sure
this breaks plpgsql's handling of simple expressions.
The quick and dirty solution to this would be for plpgsql to pass some
kind of planner flag that
On Wed, Sep 14, 2011 at 05:26, Kyotaro HORIGUCHI
horiguchi.kyot...@oss.ntt.co.jp wrote:
This is a review for the patch `Generate column names for
subquery expressions'
(https://commitfest.postgresql.org/action/patch_view?id=632)
Thanks for the review. :)
PS: When you send a review, you should
On Fri, Sep 16, 2011 at 3:22 PM, Joshua Berkus j...@agliodbs.com wrote:
No. pg_settings already has a couple dozen developer parameters which
nobody not on this mailing list understands. Adding the recovery parameters
to it wouldn't confuse anyone further, and would have the advantage of
On mån, 2011-09-05 at 23:42 +0300, Peter Eisentraut wrote:
On lör, 2011-09-03 at 19:58 -0400, Tom Lane wrote:
Anyway, after giving up on that I went back to plan A, namely install
regress.so and friends into $libdir. That turns out to be really quite
straightforward, though I had to hack
17 matches
Mail list logo
