logistics for beta3
in [PgSql]
|
From: Tom Lane on 5 Jul 2010 12:18 Robert Haas <robertmhaas(a)gmail.com> writes: > On Mon, Jul 5, 2010 at 11:01 AM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: >> Yeah, I hope to get that committed today. �Any later than today will not >> leave enough time for buildfarm testing before the wrap. > Hmm. So does that mean we need to get log_temp_files fixed today also? No, I'm just concerned about the possibility of needing multiple buildfarm cycles to shake out platform-specific problems with the LDFLAGS changes. The log_temp_files business doesn't have any portability risks AFAICS. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 5 Jul 2010 15:14 Andrew Dunstan wrote: > > > Marc G. Fournier wrote: >>> >>> - Someone (presumably Bruce) needs to run pgindent. Any reason to >>> wait any longer on that? >> > > The typedefs list on the buildfarm needs to be refreshed. That will > take me some time, since I wasn't aware we were about to do a > pg_indent run. > > Starting now ... > > completed. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 5 Jul 2010 20:38 On Mon, Jul 5, 2010 at 3:14 PM, Andrew Dunstan <andrew(a)dunslane.net> wrote: > Andrew Dunstan wrote: >> Marc G. Fournier wrote: >>>> - Someone (presumably Bruce) needs to run pgindent. �Any reason to >>>> wait any longer on that? >> >> The typedefs list on the buildfarm needs to be refreshed. That will take >> me some time, since I wasn't aware we were about to do a pg_indent run. >> >> Starting now ... > > completed. Cool. So, should we have Bruce go ahead and pgindent now? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Marc G. Fournier" on 5 Jul 2010 21:49 On Mon, 5 Jul 2010, Robert Haas wrote: > Cool. So, should we have Bruce go ahead and pgindent now? Yup, as that will give 3 days before wrap / branch to deal with any fall out from mit :) ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy(a)hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Peter Eisentraut on 6 Jul 2010 15:26 On mån, 2010-07-05 at 11:01 -0400, Tom Lane wrote: > Peter was suggesting that if we *stopped* using RTLD_GLOBAL then it > might be possible to use plpython2 and plpython3 concurrently in one > backend. After looking at the archives I'm not convinced that's > workable --- it sounds like not using RTLD_GLOBAL would have the > effect of breaking Python's extension scheme altogether. Yeah, plpython regression tests fail of you change RTLD_GLOBAL to RTLD_LOCAL. I will make a note in the documentation that using plpython2 and 3 together doesn't work. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: [HACKERS] logistics for beta3 Next: Buildfarm + Git tryouts |