Re: [HACKERS] [pgsql-advocacy] Audio interview
On Tue, Feb 07, 2006 at 11:43:40PM -0500, Bruce Momjian wrote: I did an audio interview today, and it is online now: http://bsdtalk.blogspot.com/2006/02/bsdtalk015-interview-with-postgresql.html Great interview. You hit a lot of the high points :) You mentioned in-place upgrade scripts. Are those in contrib/ somewhere? On GBorg? On PgFoundry? If not, could you put them somewhere? As far as converting them from shell to Perl, I'm sure you'll find a flock of volunteers to help. Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 415 235 3778 Remember to vote! ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] [pgsql-advocacy] Audio interview
David Fetter wrote: On Tue, Feb 07, 2006 at 11:43:40PM -0500, Bruce Momjian wrote: I did an audio interview today, and it is online now: http://bsdtalk.blogspot.com/2006/02/bsdtalk015-interview-with-postgresql.html Great interview. You hit a lot of the high points :) You mentioned in-place upgrade scripts. Are those in contrib/ somewhere? On GBorg? On PgFoundry? If not, could you put them /contrib/pgupgrade somewhere? As far as converting them from shell to Perl, I'm sure you'll find a flock of volunteers to help. Yea, but the problem with modifying the disk pages is still a problem. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (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 6: explain analyze is your friend
Re: [HACKERS] [pgsql-advocacy] Audio interview
On Wed, Feb 08, 2006 at 09:00:46AM -0500, Bruce Momjian wrote: David Fetter wrote: On Tue, Feb 07, 2006 at 11:43:40PM -0500, Bruce Momjian wrote: You mentioned in-place upgrade scripts. Are those in contrib/ somewhere? On GBorg? On PgFoundry? If not, could you put them /contrib/pg_upgrade I see it in the attic, but not in CVS TIP. Is there some way to get it back? Or should it go somewhere else until it's at least slightly working? somewhere? As far as converting them from shell to Perl, I'm sure you'll find a flock of volunteers to help. Yea, but the problem with modifying the disk pages is still a problem. I understand that not everybody will choose this path, but we've gone to a *lot* of trouble--and as you pointed out, have benefitted directly from the effort--to provide pointy-hair checkboxes like the Windows port. In-place upgrade is one of those checkboxes, and I'm pretty confident that getting it working will have at a minimum the same benefits to the rest of the code that making the Windows port did. Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 415 235 3778 Remember to vote! ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] [pgsql-advocacy] Audio interview
David Fetter wrote: On Wed, Feb 08, 2006 at 09:00:46AM -0500, Bruce Momjian wrote: David Fetter wrote: On Tue, Feb 07, 2006 at 11:43:40PM -0500, Bruce Momjian wrote: You mentioned in-place upgrade scripts. Are those in contrib/ somewhere? On GBorg? On PgFoundry? If not, could you put them /contrib/pg_upgrade I see it in the attic, but not in CVS TIP. Is there some way to get it back? Or should it go somewhere else until it's at least slightly working? There is a pgfoundry project, but it appears to be dead: http://pgfoundry.org/projects/pgupgrade This would be a very fine project for someone to pick up (maybe one of the corporate supporters could sponsor someone to work on it?) cheers andrew ---(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] [pgsql-advocacy] Audio interview
On Feb 8, 2006, at 7:00 AM, Bruce Momjian wrote: David Fetter wrote: On Tue, Feb 07, 2006 at 11:43:40PM -0500, Bruce Momjian wrote: I did an audio interview today, and it is online now: http://bsdtalk.blogspot.com/2006/02/bsdtalk015-interview-with- postgresql.html Great interview. You hit a lot of the high points :) You mentioned in-place upgrade scripts. Are those in contrib/ somewhere? On GBorg? On PgFoundry? If not, could you put them /contrib/pgupgrade somewhere? As far as converting them from shell to Perl, I'm sure you'll find a flock of volunteers to help. Yea, but the problem with modifying the disk pages is still a problem. Maybe this is totally crazy, but for those not using slony but are using incremental backup and want to upgrade without doing a time consuming dump / reload (this is not actually a problem for me as my data is not so large that a dump reload is a huge problem) would it be possible to apply pgupgrade to the physical backup before you restore, then also alter each WAL record as it is restored so that it restores all new pages in the new format. Then you could do all the work on a different box and quickly switch over to it after the restore is complete. You could eliminate most of the downtime. Is that even feasible? Not something that would help me now but it might make some people very happy (and maybe someday I will need it as well.) Rick ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] [pgsql-advocacy] Audio interview
David Fetter wrote: On Wed, Feb 08, 2006 at 09:00:46AM -0500, Bruce Momjian wrote: David Fetter wrote: On Tue, Feb 07, 2006 at 11:43:40PM -0500, Bruce Momjian wrote: You mentioned in-place upgrade scripts. Are those in contrib/ somewhere? On GBorg? On PgFoundry? If not, could you put them /contrib/pg_upgrade I see it in the attic, but not in CVS TIP. Is there some way to get it back? Or should it go somewhere else until it's at least slightly working? I think from cvsweb you can get to the Attic files. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (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 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
