Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.postgresql > #396
| From | Don Y <this@isnotme.com> |
|---|---|
| Newsgroups | comp.databases.postgresql |
| Subject | Re: scan into many tables |
| Date | 2012-07-22 12:54 -0700 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <juhlos$a0j$1@speranza.aioe.org> (permalink) |
| References | (2 earlier) <jtpr8r$4jv$2@dont-email.me> <87eho4844v.fsf@einstein.gmurray.org.uk> <3zC*BTVau@news.chiark.greenend.org.uk> <juhdbb$lvb$1@speranza.aioe.org> <a72uqjFh73U1@mid.individual.net> |
Hi Hans, On 7/22/2012 11:24 AM, Hans Castorp wrote: > Don Y wrote on 22.07.2012 19:30: >> It's a bit of a chore dumping and reloading >> an entire database (depending on size and secondary storage you have >> available to you) but (so far), so far, the process seems to go without >> a hitch. > > Since 8.4 and pg_upgrade, upgrades have become much less painful. I'm not sure I "trust" pg_upgrade, entirely, when it comes to the "universe of potential databases/sets" it might encounter. E.g., I have several custom base types that I use. So, as part of each upgrade, I dig through the sources to see what, if anything, in the "type interface" may have changed to be sure my existing types will continue to work when imported to the new implementation. I find the dump + reload option is the most reassuring one (to me) as I *know* that my code will rexamine the dumped data as it is being reloaded. I don't have to worry that some subtle change will bite me *after* it's in place (without a way of returning to the known, working configuration). And, of course, pg_upgrade doesn't help you *build* the new binaries (which Matthew might require)
Back to comp.databases.postgresql | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
scan into many tables Greg Hennessy <greg.hennessy@cox.net> - 2012-07-13 16:11 +0000
Re: scan into many tables Hans Castorp <REWYRLXHEGHO@spammotel.com> - 2012-07-13 18:37 +0200
Re: scan into many tables Greg Hennessy <greg.hennessy@cox.net> - 2012-07-13 18:54 +0000
Re: scan into many tables Greg Hennessy <greg.hennessy@cox.net> - 2012-07-13 20:48 +0000
Re: scan into many tables Matthew Woodcraft <mattheww@chiark.greenend.org.uk> - 2012-07-13 17:51 +0100
Re: scan into many tables Greg Hennessy <greg.hennessy@cox.net> - 2012-07-13 19:00 +0000
Re: scan into many tables Matthew Woodcraft <mattheww@chiark.greenend.org.uk> - 2012-07-13 22:15 +0100
Re: scan into many tables Graham Murray <newspost@gmurray.org.uk> - 2012-07-22 11:46 +0100
Re: scan into many tables Matthew Woodcraft <mattheww@chiark.greenend.org.uk> - 2012-07-22 13:09 +0100
Re: scan into many tables Robert Klemme <shortcutter@googlemail.com> - 2012-07-22 18:55 +0200
Re: scan into many tables Matthew Woodcraft <mattheww@chiark.greenend.org.uk> - 2012-07-22 21:07 +0100
Re: scan into many tables Don Y <this@isnotme.com> - 2012-07-22 10:30 -0700
Re: scan into many tables Hans Castorp <REWYRLXHEGHO@spammotel.com> - 2012-07-22 20:24 +0200
Re: scan into many tables Don Y <this@isnotme.com> - 2012-07-22 12:54 -0700
Re: scan into many tables Greg Hennessy <greg.hennessy@cox.net> - 2012-07-22 22:57 +0000
Re: scan into many tables Jasen Betts <jasen@xnet.co.nz> - 2012-07-14 02:55 +0000
csiph-web