| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pl/python improvements |
| Date: | 2010-12-07 21:50:42 |
| Message-ID: | 1291758642.19991.9.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2010-12-07 at 20:17 +0100, Jan Urbański wrote:
> no, no patch(es) yet. I'm going through plpython.c trying as best I can
> to improve things there. I'll have a patch (or patches) ready for the
> January commitfest, but I thought I'd open up a discussion already to
> spare me having to redo features because the way I attacked the problem
> is a dead end. Be warned, this ended up being a very long email...
This all sounds very nice (especially since I had many of the same items
on my todo list to tackle after Christmas or so). But I think this
would be massively simpler if you created a separate patch/branch/email
thread for each feature or change.
> The code is on https://github.com/wulczer/postgres, in the plpython
> branch. I'll be rebasing it regularly, so don't be surprised by commit
> hashes changing.
I think rebasing published repositories isn't encouraged.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-12-07 22:00:42 | Re: pl/python improvements |
| Previous Message | Tom Lane | 2010-12-07 21:50:13 | Re: pg_execute_from_file review |