Re: [HACKERS] Upcoming back branch releases
On Sun, Mar 16, 2014 at 3:20 AM, MauMau maumau...@gmail.com wrote: eFrom: Tom Lane t...@sss.pgh.pa.us After some discussion, the core committee has concluded that the WAL-replay bug fixed in commit 6bfa88acd3df830a5f7e8677c13512b1b50ae813 is indeed bad enough to justify near-term update releases. Since there seems no point in being slow about it, tarballs will be wrapped Monday (3/17) for public announcement Thursday (3/20). Regarding: Prevent intermittent could not reserve shared memory region failures on recent Windows versions (MauMau) Could you include the patch I sent for 9.0/9.1 in response to Magnus san? http://www.postgresql.org/message-id/9C709659FE3C4B8DA7135C6F307B83 F5@maumau Hi! I just applied this patch. Apologies for the delay, and thanks for the reminder! -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Re: [HACKERS] Upcoming back branch releases
eFrom: Tom Lane t...@sss.pgh.pa.us After some discussion, the core committee has concluded that the WAL-replay bug fixed in commit 6bfa88acd3df830a5f7e8677c13512b1b50ae813 is indeed bad enough to justify near-term update releases. Since there seems no point in being slow about it, tarballs will be wrapped Monday (3/17) for public announcement Thursday (3/20). Regarding: Prevent intermittent could not reserve shared memory region failures on recent Windows versions (MauMau) Could you include the patch I sent for 9.0/9.1 in response to Magnus san? http://www.postgresql.org/message-id/9C709659FE3C4B8DA7135C6F307B83F5@maumau Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Upcoming back-branch releases
On Mon, Nov 26, 2012 at 9:17 PM, Tom Lane t...@sss.pgh.pa.us wrote: We're about due for a new set of back-branch update releases. After some discussion among the packagers, it seems the best window for getting this done before the holiday season sets in is next week. Also, as previously mentioned, we're experimenting with weekday rather than over-the-weekend release windows, since this is much more convenient for Dave Page and his crew at EDB. The current plan is to wrap tarballs on Monday Dec 3 for public announcement Thursday Dec 6. There is one open bug reported by Amit Kapila that I feel is important. I'd investigated this and Simon had volunteered to fix the same. http://archives.postgresql.org/pgsql-hackers/2012-10/msg01584.php I'm not sure about the project policies about fixing known bugs before minor releases, but AFAICS this one can lead to corrupt indexes and as a consequence return wrong query results (as shown in the case by Amit). So IMHO we should fix this. Thanks, Pavan
Re: [HACKERS] Upcoming back-branch releases
On 2012-11-26 21:35:05 +0530, Pavan Deolasee wrote: On Mon, Nov 26, 2012 at 9:17 PM, Tom Lane t...@sss.pgh.pa.us wrote: We're about due for a new set of back-branch update releases. After some discussion among the packagers, it seems the best window for getting this done before the holiday season sets in is next week. Also, as previously mentioned, we're experimenting with weekday rather than over-the-weekend release windows, since this is much more convenient for Dave Page and his crew at EDB. The current plan is to wrap tarballs on Monday Dec 3 for public announcement Thursday Dec 6. There is one open bug reported by Amit Kapila that I feel is important. I'd investigated this and Simon had volunteered to fix the same. http://archives.postgresql.org/pgsql-hackers/2012-10/msg01584.php I have submitted a proposed fix for it friday: http://archives.postgresql.org/message-id/20121124155005.GA10299%40awork2.anarazel.de For some reason the web ui only shows one of the the attachements though... They also are in: http://git.postgresql.org/gitweb/?p=users/andresfreund/postgres.git;a=shortlog;h=refs/heads/bugfixes Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Upcoming back-branch releases
On Mon, Nov 26, 2012 at 5:21 PM, Andres Freund and...@2ndquadrant.com wrote: On 2012-11-26 21:35:05 +0530, Pavan Deolasee wrote: On Mon, Nov 26, 2012 at 9:17 PM, Tom Lane t...@sss.pgh.pa.us wrote: We're about due for a new set of back-branch update releases. After some discussion among the packagers, it seems the best window for getting this done before the holiday season sets in is next week. Also, as previously mentioned, we're experimenting with weekday rather than over-the-weekend release windows, since this is much more convenient for Dave Page and his crew at EDB. The current plan is to wrap tarballs on Monday Dec 3 for public announcement Thursday Dec 6. There is one open bug reported by Amit Kapila that I feel is important. I'd investigated this and Simon had volunteered to fix the same. http://archives.postgresql.org/pgsql-hackers/2012-10/msg01584.php I have submitted a proposed fix for it friday: http://archives.postgresql.org/message-id/20121124155005.GA10299%40awork2.anarazel.de For some reason the web ui only shows one of the the attachements though... Did you by any chance use git-send-email to send it? That one is known to confuse how majordomo sticks it in the mbox files that are then later used to generate the archives... (Yes, a better way to deal with that is in the works. But it would certainly help to know if that's how the email was created, so we have more datapoints) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Upcoming back-branch releases
On 2012-11-26 17:27:11 +0100, Magnus Hagander wrote: On Mon, Nov 26, 2012 at 5:21 PM, Andres Freund and...@2ndquadrant.com wrote: On 2012-11-26 21:35:05 +0530, Pavan Deolasee wrote: On Mon, Nov 26, 2012 at 9:17 PM, Tom Lane t...@sss.pgh.pa.us wrote: We're about due for a new set of back-branch update releases. After some discussion among the packagers, it seems the best window for getting this done before the holiday season sets in is next week. Also, as previously mentioned, we're experimenting with weekday rather than over-the-weekend release windows, since this is much more convenient for Dave Page and his crew at EDB. The current plan is to wrap tarballs on Monday Dec 3 for public announcement Thursday Dec 6. There is one open bug reported by Amit Kapila that I feel is important. I'd investigated this and Simon had volunteered to fix the same. http://archives.postgresql.org/pgsql-hackers/2012-10/msg01584.php I have submitted a proposed fix for it friday: http://archives.postgresql.org/message-id/20121124155005.GA10299%40awork2.anarazel.de For some reason the web ui only shows one of the the attachements though... Did you by any chance use git-send-email to send it? That one is known to confuse how majordomo sticks it in the mbox files that are then later used to generate the archives... (Yes, a better way to deal with that is in the works. But it would certainly help to know if that's how the email was created, so we have more datapoints) No git-send-email in this case (although I used it in the past and likely will use it again). Mutt instead. The attachements were generated by git format-patch HEAD~2 and then normally attached to the email. format-patch is internally used by send-email though, so that might be a hint... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Upcoming back-branch releases
Andres Freund escribió: On 2012-11-26 17:27:11 +0100, Magnus Hagander wrote: On Mon, Nov 26, 2012 at 5:21 PM, Andres Freund and...@2ndquadrant.com wrote: I have submitted a proposed fix for it friday: http://archives.postgresql.org/message-id/20121124155005.GA10299%40awork2.anarazel.de For some reason the web ui only shows one of the the attachements though... Did you by any chance use git-send-email to send it? That one is known to confuse how majordomo sticks it in the mbox files that are then later used to generate the archives... (Yes, a better way to deal with that is in the works. But it would certainly help to know if that's how the email was created, so we have more datapoints) No git-send-email in this case (although I used it in the past and likely will use it again). Mutt instead. The attachements were generated by git format-patch HEAD~2 and then normally attached to the email. format-patch is internally used by send-email though, so that might be a hint... The problem is that those files start with the infamous ^From header line which Mhonarc is so old-fashioned about, so the patches ended up as separate emails. Note the attachment in the email linked above is empty. You can see the patches here: http://archives.postgresql.org/pgsql-hackers/2012-11/msg01278.php http://archives.postgresql.org/pgsql-hackers/2012-11/msg01279.php -- Álvaro Herrerahttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Upcoming back-branch releases
On Mon, Aug 15, 2005 at 01:06:15PM -0400, Tom Lane wrote: So, if you've got any pending patches for the back branches, now would be a good time to get 'em done up and sent in. http://archives.postgresql.org/pgsql-patches/2005-07/msg00291.php -- marko ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Upcoming back-branch releases
Tom Lane wrote: The core committee has agreed that we need to do a set of releases in the back branches soon --- certainly 8.0 has accumulated a critical mass of changes since 8.0.3, and probably there's enough to justify updates of the 7.* branches too. We hope to get these out sometime next week, after the first 8.1 beta release is done. So, if you've got any pending patches for the back branches, now would be a good time to get 'em done up and sent in. I am going to look urgently at fixing the no IPv6 on Windows bug that came up yesterday. cheers andrew ---(end of broadcast)--- TIP 1: 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] Upcoming back-branch releases
On Monday 15 August 2005 13:06, Tom Lane wrote:
The core committee has agreed that we need to do a set of releases
in the back branches soon --- certainly 8.0 has accumulated a critical
mass of changes since 8.0.3, and probably there's enough to justify
updates of the 7.* branches too. We hope to get these out sometime
next week, after the first 8.1 beta release is done.
So, if you've got any pending patches for the back branches, now would
be a good time to get 'em done up and sent in.
I installed 7.3.10 from source the other day, and noticed that at the end of
initdb it told me I could register my install and check out the mailing
lists, both a 404'd web pages. Does anyone think we should update these older
versions with more current information?
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
Re: [HACKERS] Upcoming back-branch releases
Robert Treat wrote: I installed 7.3.10 from source the other day, and noticed that at the end of initdb it told me I could register my install and check out the mailing lists, both a 404'd web pages. Does anyone think we should update these older versions with more current information? And also to redirect those old URLs to the right place, if possible. Surely writing a few Redirect lines in an apache config file isn't beyond us. cheers andrew ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Upcoming back-branch releases
The core committee has agreed that we need to do a set of releases in the back branches soon --- certainly 8.0 has accumulated a critical mass of changes since 8.0.3, and probably there's enough to justify updates of the 7.* branches too. We hope to get these out sometime next week, after the first 8.1 beta release is done. So, if you've got any pending patches for the back branches, now would be a good time to get 'em done up and sent in. Is there any call to backport the pg_dump object sorting improvements? It could be considered a 'bug' I guess, and could help people upgrading from 7.4... Chris ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Upcoming back-branch releases
On Mon, 15 Aug 2005, Robert Treat wrote: On Monday 15 August 2005 13:06, Tom Lane wrote: The core committee has agreed that we need to do a set of releases in the back branches soon --- certainly 8.0 has accumulated a critical mass of changes since 8.0.3, and probably there's enough to justify updates of the 7.* branches too. We hope to get these out sometime next week, after the first 8.1 beta release is done. So, if you've got any pending patches for the back branches, now would be a good time to get 'em done up and sent in. I installed 7.3.10 from source the other day, and noticed that at the end of initdb it told me I could register my install and check out the mailing lists, both a 404'd web pages. Does anyone think we should update these older versions with more current information? What page did it point you to? If nothing else, we can add a redirect to a more appropriate location so that ppl don't get the 404 errors ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Upcoming back-branch releases
Christopher Kings-Lynne [EMAIL PROTECTED] writes: Is there any call to backport the pg_dump object sorting improvements? My recollection is that that change was way too invasive to be reasonable for a back-port. The solutions used for circular reference situations (various ALTER commands) probably don't exist very far back anyway. It could be considered a 'bug' I guess, and could help people upgrading from 7.4... They could just use the 8.0 pg_dump for that. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Upcoming back-branch releases
My recollection is that that change was way too invasive to be reasonable for a back-port. The solutions used for circular reference situations (various ALTER commands) probably don't exist very far back anyway. Nah, all you need to do is take the 8.0 pg_dump, hard-code that --use-set-session-authorization is always enabled, and remove use of pg_get_serial_sequence IIRC... It could be considered a 'bug' I guess, and could help people upgrading from 7.4... They could just use the 8.0 pg_dump for that. Yep. But who knows to do that? :) My 2c : we have an archive of statically compiled pg_dump binaries on postgresql.org. Cheers, Chris ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Upcoming back-branch releases
Marc G. Fournier [EMAIL PROTECTED] writes: On Mon, 15 Aug 2005, Robert Treat wrote: I installed 7.3.10 from source the other day, and noticed that at the end of initdb it told me I could register my install and check out the mailing lists, both a 404'd web pages. Does anyone think we should update these older versions with more current information? What page did it point you to? If nothing else, we can add a redirect to a more appropriate location so that ppl don't get the 404 errors ... The 7.3 version of register.txt is attached. We could update it, or get rid of it completely as later branches did ... regards, tom lane PostgreSQL has a web site at http://www.postgresql.org/ which carries details on the latest release, upcoming features, and other information to make your work or play with PostgreSQL more productive. Please check the following URL for a listing of the current user-support mailing lists: http://www.ca.postgresql.org/users-lounge/index.html#maillist All of the mailing lists are currently archived and viewable at: http://archives.postgresql.org/ And, so that we have an idea of who is using what, please connect to the following registration URL: http://www.pgsql.com/register/submit.php Thank you for choosing PostgreSQL, the most advanced open source database engine. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Upcoming back-branch releases
Marc G. Fournier [EMAIL PROTECTED] writes: I'd vote to get rid of it ... the concept of 'registering' might throw some for a loop ... Works for me; will do that in the 7.3 and 7.2 branches. It'd still be a good idea to put in some redirects to make those old URLs do something again. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Upcoming back-branch releases
I'd vote to get rid of it ... the concept of 'registering' might throw some for a loop ... On Mon, 15 Aug 2005, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: On Mon, 15 Aug 2005, Robert Treat wrote: I installed 7.3.10 from source the other day, and noticed that at the end of initdb it told me I could register my install and check out the mailing lists, both a 404'd web pages. Does anyone think we should update these older versions with more current information? What page did it point you to? If nothing else, we can add a redirect to a more appropriate location so that ppl don't get the 404 errors ... The 7.3 version of register.txt is attached. We could update it, or get rid of it completely as later branches did ... regards, tom lane PostgreSQL has a web site at http://www.postgresql.org/ which carries details on the latest release, upcoming features, and other information to make your work or play with PostgreSQL more productive. Please check the following URL for a listing of the current user-support mailing lists: http://www.ca.postgresql.org/users-lounge/index.html#maillist All of the mailing lists are currently archived and viewable at: http://archives.postgresql.org/ And, so that we have an idea of who is using what, please connect to the following registration URL: http://www.pgsql.com/register/submit.php Thank you for choosing PostgreSQL, the most advanced open source database engine. Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Upcoming back-branch releases
On Mon, 15 Aug 2005, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: I'd vote to get rid of it ... the concept of 'registering' might throw some for a loop ... Works for me; will do that in the 7.3 and 7.2 branches. It'd still be a good idea to put in some redirects to make those old URLs do something again. Now redirected to http://www.postgresql.org ... if someone has a better place to redirect it to, please feel free to suggest it ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
