Re: [HACKERS] 7.4 feature freeze is here
Folks, You might like to mention that (as far as I can tell) ECPG is now safe for pthreads on Linux and FreeBSD. The recursive mutex locks are removed, so even platforms that implement the earlier version of pthreads ought to work as well, once configure supports them (anyone care to actually test this assertion?) I don't quite understand this. This doesn't mean that *postgresql* is threaded, does it? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] 7.4 feature freeze is here
On Fri, 4 Jul 2003 04:03 pm, Josh Berkus wrote: I don't quite understand this. This doesn't mean that *postgresql* is threaded, does it? I was just referring to the client interfaces ECPG and libpq. AFAIK the back-end is not threaded (and I'm beginning to understand why not). So my app starts multiple threads of execution through the ECPG libs... the ECPG libs (and libpq) start multiple sockets to the back-end - one for each thread. No changes to the back-end. That's my understanding - Lee did most of the work, so maybe he can confirm that. Regards, Philip Yarra. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] 7.4 feature freeze is here
On Thu, Jul 03, 2003 at 10:18:23 +0800, Christopher Kings-Lynne [EMAIL PROTECTED] wrote: It might be killer than that PHP support for Apache2 requires that all PHP modules be thread-safe... Is that true if you are using the prefork MPM? ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 feature freeze is here
On Thu, Jul 03, 2003 at 10:18:23 +0800, Christopher Kings-Lynne [EMAIL PROTECTED] wrote: It might be killer than that PHP support for Apache2 requires that all PHP modules be thread-safe... Is that true if you are using the prefork MPM? Dunno. Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.4 feature freeze is here
Once you folks are done going through the remaining list of patches, can
we get someone to send a rough list of new features in 7.4 sent over to
-advocacy? Please feel free to highlight any items that you think
warrant special notice from a technical standpoint. Thanks in advance,
Robert Treat
On Tue, 2003-07-01 at 17:26, Tom Lane wrote:
The Postgres core committee would like to announce that we are now in
feature-freeze mode for the 7.4 release.
All patches already received in pgsql-patches will be considered in the
usual fashion (and yes, we'll allow some slack for fixing problems in
them). New features arriving in the future will be held for 7.5.
Feel free to keep sending patches that fix bugs or improve
documentation; only new features are out.
The plan is to spend the next two weeks cleaning things up (bug fixes,
documentation, etc) with a formal beta release scheduled on or about
July 15.
Final release of 7.4 will be whenever it seems ready, as usual.
regards, tom lane
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [HACKERS] 7.4 feature freeze is here
I usually do it, but it might take a week to put together.
---
Robert Treat wrote:
Once you folks are done going through the remaining list of patches, can
we get someone to send a rough list of new features in 7.4 sent over to
-advocacy? Please feel free to highlight any items that you think
warrant special notice from a technical standpoint. Thanks in advance,
Robert Treat
On Tue, 2003-07-01 at 17:26, Tom Lane wrote:
The Postgres core committee would like to announce that we are now in
feature-freeze mode for the 7.4 release.
All patches already received in pgsql-patches will be considered in the
usual fashion (and yes, we'll allow some slack for fixing problems in
them). New features arriving in the future will be held for 7.5.
Feel free to keep sending patches that fix bugs or improve
documentation; only new features are out.
The plan is to spend the next two weeks cleaning things up (bug fixes,
documentation, etc) with a formal beta release scheduled on or about
July 15.
Final release of 7.4 will be whenever it seems ready, as usual.
regards, tom lane
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [HACKERS] 7.4 feature freeze is here
Bruce Momjian wrote: I usually do it, but it might take a week to put together. --- Robert Treat wrote: Once you folks are done going through the remaining list of patches, can we get someone to send a rough list of new features in 7.4 sent over to -advocacy? Please feel free to highlight any items that you think warrant special notice from a technical standpoint. Thanks in advance, Hi Bruce, please also send it to pgadmin-hackers, so we can be sure to know all features. We'll try to release at the same time that 7.4 is released. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 feature freeze is here
On Thu, 3 Jul 2003 12:14 am, you wrote: I usually do it, but it might take a week to put together. You might like to mention that (as far as I can tell) ECPG is now safe for pthreads on Linux and FreeBSD. The recursive mutex locks are removed, so even platforms that implement the earlier version of pthreads ought to work as well, once configure supports them (anyone care to actually test this assertion?) I don't know if other people think this is a killer feature but it means people porting from embedded SQL platforms where thread support has existed for some time (like Informix and Sybase) will have an easier time of it. Regards, Philip Yarra. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] 7.4 feature freeze is here
-Original Message- From: Philip Yarra [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 5:17 PM To: Bruce Momjian Cc: [EMAIL PROTECTED] Subject: Re: [HACKERS] 7.4 feature freeze is here On Thu, 3 Jul 2003 12:14 am, you wrote: I usually do it, but it might take a week to put together. You might like to mention that (as far as I can tell) ECPG is now safe for pthreads on Linux and FreeBSD. The recursive mutex locks are removed, so even platforms that implement the earlier version of pthreads ought to work as well, once configure supports them (anyone care to actually test this assertion?) I don't know if other people think this is a killer feature but it means people porting from embedded SQL platforms where thread support has existed for some time (like Informix and Sybase) will have an easier time of it. This is happy joy. It's a killer feature *for me*. Down upon my knees, I kiss gently even the dirty boots of those that did the work. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 feature freeze is here
Yes, I grab this info from the CVS logs, and I certainly mentioned it in the commit. --- Philip Yarra wrote: On Thu, 3 Jul 2003 12:14 am, you wrote: I usually do it, but it might take a week to put together. You might like to mention that (as far as I can tell) ECPG is now safe for pthreads on Linux and FreeBSD. The recursive mutex locks are removed, so even platforms that implement the earlier version of pthreads ought to work as well, once configure supports them (anyone care to actually test this assertion?) I don't know if other people think this is a killer feature but it means people porting from embedded SQL platforms where thread support has existed for some time (like Informix and Sybase) will have an easier time of it. Regards, Philip Yarra. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] 7.4 feature freeze is here
Read the HISTORY file - there's a few things.
Chris
- Original Message -
From: Robert Treat [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 02, 2003 9:27 PM
Subject: Re: [HACKERS] 7.4 feature freeze is here
Once you folks are done going through the remaining list of patches, can
we get someone to send a rough list of new features in 7.4 sent over to
-advocacy? Please feel free to highlight any items that you think
warrant special notice from a technical standpoint. Thanks in advance,
Robert Treat
On Tue, 2003-07-01 at 17:26, Tom Lane wrote:
The Postgres core committee would like to announce that we are now in
feature-freeze mode for the 7.4 release.
All patches already received in pgsql-patches will be considered in the
usual fashion (and yes, we'll allow some slack for fixing problems in
them). New features arriving in the future will be held for 7.5.
Feel free to keep sending patches that fix bugs or improve
documentation; only new features are out.
The plan is to spend the next two weeks cleaning things up (bug fixes,
documentation, etc) with a formal beta release scheduled on or about
July 15.
Final release of 7.4 will be whenever it seems ready, as usual.
regards, tom lane
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] 7.4 feature freeze is here
You might like to mention that (as far as I can tell) ECPG is now safe for pthreads on Linux and FreeBSD. The recursive mutex locks are removed, so even platforms that implement the earlier version of pthreads ought to work as well, once configure supports them (anyone care to actually test this assertion?) I don't know if other people think this is a killer feature but it means people porting from embedded SQL platforms where thread support has existed for some time (like Informix and Sybase) will have an easier time of it. It might be killer than that PHP support for Apache2 requires that all PHP modules be thread-safe... Chris ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[HACKERS] 7.4 feature freeze is here
The Postgres core committee would like to announce that we are now in feature-freeze mode for the 7.4 release. All patches already received in pgsql-patches will be considered in the usual fashion (and yes, we'll allow some slack for fixing problems in them). New features arriving in the future will be held for 7.5. Feel free to keep sending patches that fix bugs or improve documentation; only new features are out. The plan is to spend the next two weeks cleaning things up (bug fixes, documentation, etc) with a formal beta release scheduled on or about July 15. Final release of 7.4 will be whenever it seems ready, as usual. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
