Re: [HACKERS] Time for 7.2.1?
On Tue, 19 Mar 2002, Bruce Momjian wrote: > Oleg Bartunov wrote: > > On Tue, 19 Mar 2002, Bruce Momjian wrote: > > > > > Oleg Bartunov wrote: > > > > Bruce, > > > > > > > > we have something to add. It's quite important for users of our tsearch module. > > > > Too late ? > > > > > > For 7.2.1, I don't think it is too late but I don't think we can wait > > > days. > > > > Don't wait. It's below: > > > > Users of contrib/tsearch needs after upgrading of module (compiling, installing) > > to perform sql command: > > update pg_amop set amopreqcheck = true where amopclaid = > > (select oid from pg_opclass where opcname = 'gist_txtidx_ops'); > > Oleg, sorry, I don't understand where this should appear. In the README > file, and if so, where? Is this something only for people upgrading > from 7.2? Sorry Bruce, I was unclear. I have attached patch to Readme.tsearch Also, It'd be worth to mention in Changes to point users of tsearch about importang upgrade notices. > > Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 *** README.tsearch.orig Fri Feb 8 01:11:42 2002 --- README.tsearch Tue Mar 19 16:36:17 2002 *** *** 4,9 --- 4,18 All work was done by Teodor Sigaev ([EMAIL PROTECTED]) and Oleg Bartunov ([EMAIL PROTECTED]). + CHANGES: + + To upgrade from 7.2 to 7.2.1 one needs to perform following sql + (after compiling and installing contrib/tsearch): + + update pg_amop set amopreqcheck = true where amopclaid = + (select oid from pg_opclass where opcname = 'gist_txtidx_ops'); + + IMPORTANT NOTICE: This is a first step of our work on integration of OpenFTS ---(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] Time for 7.2.1?
Bruce, we have something to add. It's quite important for users of our tsearch module. Too late ? On Mon, 18 Mar 2002, Bruce Momjian wrote: > > OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want > any special text about the sequence bug fix, or just mention in the > announcement that all 7.2 people should upgrade? > > --- > > Bruce Momjian wrote: > > Tom Lane wrote: > > > I believe we've now committed fixes for all the "must fix" items there > > > were for 7.2.1. Does anyone have any reasons to hold up 7.2.1 more, > > > or are we ready to go? > > > > I need to brand 7.2.1 --- will do tomorrow. > > > > -- > > Bruce Momjian| http://candle.pha.pa.us > > [EMAIL PROTECTED] | (610) 853-3000 > > + If your life is a hard drive, | 830 Blythe Avenue > > + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 > > > > ---(end of broadcast)--- > > TIP 6: Have you searched our list archives? > > > > http://archives.postgresql.org > > > > ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Time for 7.2.1?
OK, patch applied to 7.2.1 only --- no need to have that mentioned in 7.3 README.tsearch. HISTORY/release.sgml updated in both branches: contrib/tsearch dictionary improvements, see README.tsearch for an additional installation step (Thomas T. Thai, Teodor Sigaev) --- Oleg Bartunov wrote: > On Tue, 19 Mar 2002, Bruce Momjian wrote: > > > Oleg Bartunov wrote: > > > On Tue, 19 Mar 2002, Bruce Momjian wrote: > > > > > > > Oleg Bartunov wrote: > > > > > Bruce, > > > > > > > > > > we have something to add. It's quite important for users of our tsearch >module. > > > > > Too late ? > > > > > > > > For 7.2.1, I don't think it is too late but I don't think we can wait > > > > days. > > > > > > Don't wait. It's below: > > > > > > Users of contrib/tsearch needs after upgrading of module (compiling, installing) > > > to perform sql command: > > > update pg_amop set amopreqcheck = true where amopclaid = > > > (select oid from pg_opclass where opcname = 'gist_txtidx_ops'); > > > > Oleg, sorry, I don't understand where this should appear. In the README > > file, and if so, where? Is this something only for people upgrading > > from 7.2? > > Sorry Bruce, I was unclear. I have attached patch to Readme.tsearch > Also, It'd be worth to mention in Changes to point users of tsearch > about importang upgrade notices. > > > > > > > Regards, > Oleg > _ > Oleg Bartunov, sci.researcher, hostmaster of AstroNet, > Sternberg Astronomical Institute, Moscow University (Russia) > Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ > phone: +007(095)939-16-83, +007(095)939-23-83 Content-Description: [ Attachment, skipping... ] -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Time for 7.2.1?
Oleg Bartunov wrote: > On Tue, 19 Mar 2002, Bruce Momjian wrote: > > > Oleg Bartunov wrote: > > > Bruce, > > > > > > we have something to add. It's quite important for users of our tsearch module. > > > Too late ? > > > > For 7.2.1, I don't think it is too late but I don't think we can wait > > days. > > Don't wait. It's below: > > Users of contrib/tsearch needs after upgrading of module (compiling, installing) > to perform sql command: > update pg_amop set amopreqcheck = true where amopclaid = > (select oid from pg_opclass where opcname = 'gist_txtidx_ops'); Oleg, sorry, I don't understand where this should appear. In the README file, and if so, where? Is this something only for people upgrading from 7.2? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(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] Time for 7.2.1?
On Tue, 19 Mar 2002, Bruce Momjian wrote: > Oleg Bartunov wrote: > > Bruce, > > > > we have something to add. It's quite important for users of our tsearch module. > > Too late ? > > For 7.2.1, I don't think it is too late but I don't think we can wait > days. I'll do a wrap on Friday, if Oleg wants to get his stuff in and tested? ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Time for 7.2.1?
Oleg Bartunov wrote: > Bruce, > > we have something to add. It's quite important for users of our tsearch module. > Too late ? For 7.2.1, I don't think it is too late but I don't think we can wait days. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Time for 7.2.1?
D'Arcy J.M. Cain wrote: > On March 18, 2002 06:12 pm, Bruce Momjian wrote: > > OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want > > any special text about the sequence bug fix, or just mention in the > > announcement that all 7.2 people should upgrade? > > Does this mean that I can start putting fixes and upgrades into PyGreSQL? Sure, main CVS is open for 7.3. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Time for 7.2.1?
On March 18, 2002 06:12 pm, Bruce Momjian wrote: > OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want > any special text about the sequence bug fix, or just mention in the > announcement that all 7.2 people should upgrade? Does this mean that I can start putting fixes and upgrades into PyGreSQL? -- D'Arcy J.M. Cain| Democracy is three wolves http://www.druid.net/darcy/| and a sheep voting on +1 416 425 1212 (DoD#0082)(eNTP) | what's for dinner. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Time for 7.2.1?
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want > > any special text about the sequence bug fix, or just mention in the > > announcement that all 7.2 people should upgrade? > > The first change item should maybe be more explicit, say > > Ensure that sequence counters do not go backwards after a crash > > Otherwise I think it's fine. BTW, the bug exists in 7.1 as well. Done. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Time for 7.2.1?
Bruce Momjian <[EMAIL PROTECTED]> writes: > OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want > any special text about the sequence bug fix, or just mention in the > announcement that all 7.2 people should upgrade? The first change item should maybe be more explicit, say Ensure that sequence counters do not go backwards after a crash Otherwise I think it's fine. BTW, the bug exists in 7.1 as well. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Time for 7.2.1?
OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want any special text about the sequence bug fix, or just mention in the announcement that all 7.2 people should upgrade? --- Bruce Momjian wrote: > Tom Lane wrote: > > I believe we've now committed fixes for all the "must fix" items there > > were for 7.2.1. Does anyone have any reasons to hold up 7.2.1 more, > > or are we ready to go? > > I need to brand 7.2.1 --- will do tomorrow. > > -- > Bruce Momjian| http://candle.pha.pa.us > [EMAIL PROTECTED] | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Time for 7.2.1?
Tom Lane wrote: > I believe we've now committed fixes for all the "must fix" items there > were for 7.2.1. Does anyone have any reasons to hold up 7.2.1 more, > or are we ready to go? I need to brand 7.2.1 --- will do tomorrow. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Time for 7.2.1?
I believe we've now committed fixes for all the "must fix" items there were for 7.2.1. Does anyone have any reasons to hold up 7.2.1 more, or are we ready to go? regards, tom lane ---(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] Time for 7.2.1?
Thomas Lockhart <[EMAIL PROTECTED]> writes: > It is somewhat complicated by the fact that my code tree is pretty > massively changed in this area as I implement an int64-based date/time > storage alternative to the float64 scheme we use now. The alternative > would be enabled with something like #ifdef HAVE_INT64_TIMESTAMP. > Benefits would include having a predictable precision behavior for all > allowed dates and times. Interesting. But if this is just an #ifdef, I can see some serious problems coming up the first time someone runs a backend compiled with one set of timestamp code in a database created with the other. May I suggest that the timestamp representation be identified in a field added to pg_control? That's how we deal with other options that affect database contents ... regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Time for 7.2.1?
> Well, we were gonna release it last weekend, but now it's waiting on > sequence fixes (currently being tested). And Lockhart may also wish to > hold it up while he looks at the recently reported timestamp_part > problem. (Thomas, are you considering backpatching that?) One way > or another I'd expect it next week sometime. I'll consider backpatching once I have a chance to dive in. It is somewhat complicated by the fact that my code tree is pretty massively changed in this area as I implement an int64-based date/time storage alternative to the float64 scheme we use now. The alternative would be enabled with something like #ifdef HAVE_INT64_TIMESTAMP. Benefits would include having a predictable precision behavior for all allowed dates and times. - Thomas ---(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] Time for 7.2.1?
"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: > is there any further word on 7.2.1, at this point? haven't seen mention > of it on the list in a while? is it still waiting on something big? Well, we were gonna release it last weekend, but now it's waiting on sequence fixes (currently being tested). And Lockhart may also wish to hold it up while he looks at the recently reported timestamp_part problem. (Thomas, are you considering backpatching that?) One way or another I'd expect it next week sometime. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] Time for 7.2.1?
is there any further word on 7.2.1, at this point? haven't seen mention of it on the list in a while? is it still waiting on something big? -tfo Bruce Momjian wrote: > Applied to current and 7.2.X. Thanks. > > (No delay for /contrib commits from maintainers.) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
