[ADMIN] Upgrade problems with OID type ...
Hi all! I'm trying to upgrade from 7.3.2 to 7.4.3 but I've a problem with a database (1 I know, there could be more) containing a table with an oid type field. I run the migration doing: ../bin/pg_dumpall -o -p 5432 | /apps/pgs-7.4.3/bin/psql -d template1 -p 5433 1>/tmp/out 2>/tmp/err The command runs fine, with no ERRORS on the output files, but when the user accesses their application (web) the images he was storing does'nt appear, and I can see errors like this on the logfile: 2004-07-06 09:54:52 ERROR: large object 417988 does not exist First I was doing the dump without the -o, but now I use it and the problem persists ... Ideas? Thanks in advance ... -- Daniel Rubio Rodríguez OASI (Organisme Autònom Per la Societat de la Informació) c/ Assalt, 12 43003 - Tarragona Tef.: 977.244.007 - Fax: 977.224.517 e-mail: drubio a oasi.org ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[ADMIN] Replication in main PostgreSQL codebase
Hello all! I apologise in advance if any of my questions are in a FAQ somewhere - I haven't seen them... Does anyone know when (if ever) replication support will be added to the main PostgreSQL codebase? Is there any chance it'll be included in the upcoming 7.5 release? I've taken a look at the replication solutions already available, including the sterling effort made on Slony-I, but we're really looking for integrated, base-level support rather than an add-in. Cheers! ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [ADMIN] Replication in main PostgreSQL codebase
After a long battle with technology, [EMAIL PROTECTED] ("Matt Browne"), an earthling,
wrote:
> I apologise in advance if any of my questions are in a FAQ somewhere - I
> haven't seen them...
>
> Does anyone know when (if ever) replication support will be added to the
> main PostgreSQL codebase? Is there any chance it'll be included in the
> upcoming 7.5 release?
Not much of a chance.
> I've taken a look at the replication solutions already available,
> including the sterling effort made on Slony-I, but we're really
> looking for integrated, base-level support rather than an add-in.
The problem is that "replication" doesn't tend to mean one thing, but
people rather have different ideas of what it means.
Jan Wieck puts it fairly nicely:
"The number of different replication solutions available supports
the theory that ``one size fits all'' is not true when it comes to
database replication."
--
let name="cbbrowne" and tld="acm.org" in name ^ "@" ^ tld;;
http://www.ntlug.org/~cbbrowne/emacs.html
You shouldn't anthropomorphize computers; they don't like it.
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [ADMIN] Replication in main PostgreSQL codebase
On 06 July 2004 16:41, Christopher Browne wrote: > > I've taken a look at the replication solutions already available, > > including the sterling effort made on Slony-I, but we're really > > looking for integrated, base-level support rather than an add-in. > > The problem is that "replication" doesn't tend to mean one > thing, but people rather have different ideas of what it means. I don't necessarily agree with that. It's true that one size hardly ever fits all, especially when it comes to implementation, but I think people have a certain replication feature set in mind when they come across a DBMS that purports to be enterprise-class... ... Just like what's been listed in the 'Urgent' section of the TODO list since (I think) 7.2, in fact. (Except perhaps the more complex features like multi-master replication.) I didn't post my original message to the pgsql-hackers list because I wanted to respect the ominous warning about trying other lists first. Not to discount your comments, Christopher, but is there anyone on this list who could give me an official and authoritative line on the inclusion of in-built replication functionality? Thanks again! ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [ADMIN] Replication in main PostgreSQL codebase
On Tue, 6 Jul 2004, Matt Browne wrote: On 06 July 2004 16:41, Christopher Browne wrote: I've taken a look at the replication solutions already available, including the sterling effort made on Slony-I, but we're really looking for integrated, base-level support rather than an add-in. The problem is that "replication" doesn't tend to mean one thing, but people rather have different ideas of what it means. I don't necessarily agree with that. It's true that one size hardly ever fits all, especially when it comes to implementation, but I think people have a certain replication feature set in mind when they come across a DBMS that purports to be enterprise-class... ... Just like what's been listed in the 'Urgent' section of the TODO list since (I think) 7.2, in fact. (Except perhaps the more complex features like multi-master replication.) I didn't post my original message to the pgsql-hackers list because I wanted to respect the ominous warning about trying other lists first. Not to discount your comments, Christopher, but is there anyone on this list who could give me an official and authoritative line on the inclusion of in-built replication functionality? Christopher is correct ... if there was such a thing as an 'end all, be all' replication solution, there wouldn't be a half a dozen different ones out there ... It would be unwise for *anyone* to state "never" as far as inclusion of built-in replication, but since the general consensus is that there is no such thing as the 'all-encompassing solution' for this, the chances of one ever coming about that would be of a scope that would be acceptable to be built-in is next to zero ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [ADMIN] Replication in main PostgreSQL codebase
Marc G. Fournier wrote: > Christopher is correct ... if there was such a thing as an 'end all, be > all' replication solution, there wouldn't be a half a dozen different ones > out there ... > > It would be unwise for *anyone* to state "never" as far as inclusion of > built-in replication, but since the general consensus is that there is no > such thing as the 'all-encompassing solution' for this, the chances of one > ever coming about that would be of a scope that would be acceptable to be > built-in is next to zero ... OK, I reworded the replication TODO section and moved it under Administration: * Improve replication solutions o Automatic failover o Load balancing o Master/slave replication o Multi-master replication o Partition data across servers o Queries across databases or servers (two-phase commit) o Allow replication over unreliable or non-persistent links -- 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 6: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] Replication in main PostgreSQL codebase
On Tue, 6 Jul 2004 17:07:33 -0300 (ADT), Marc G. Fournier <[EMAIL PROTECTED]> wrote: > It would be unwise for *anyone* to state "never" as far as inclusion of > built-in replication, but since the general consensus is that there is no > such thing as the 'all-encompassing solution' for this, the chances of one > ever coming about that would be of a scope that would be acceptable to be > built-in is next to zero ... I think what I run into is that while most of us would agree that the "one size fits all" argument is useless from a technical perspective, it's not the technical people that are usually the ones involved here. >From a "marketing" perspective, it would be useful if PostgreSQL included at least a single master, single slave replication model that was easily enabled and set up. There is a subclass of the problem that is common to most situations, which is the ability to have a "live" backup. Perhaps the 'dbmirror' component in the 'contrib' directory is enough, and it simply needs to be highlighted. It does meet some subset of the needs out there. Sadly, a lot of problems are simply marketing perceptions :/ Chris -- | Christopher Petrilli | [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [ADMIN] Replication in main PostgreSQL codebase
Christopher Browne wrote: > Jan Wieck puts it fairly nicely: > > "The number of different replication solutions available supports >the theory that ``one size fits all'' is not true when it comes to >database replication." The fact that all but one or two replication solutions out there are pretty much dead supports the theory that "one size fits most" is true. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [ADMIN] Replication in main PostgreSQL codebase
Marc G. Fournier wrote: > Christopher is correct ... if there was such a thing as an 'end all, > be all' replication solution, there wouldn't be a half a dozen > different ones out there ... Which ones are you thinking of in your count? I don't get anywhere near half a dozen. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [ADMIN] Replication in main PostgreSQL codebase
On Tue, 6 Jul 2004, Peter Eisentraut wrote: Marc G. Fournier wrote: Christopher is correct ... if there was such a thing as an 'end all, be all' replication solution, there wouldn't be a half a dozen different ones out there ... Which ones are you thinking of in your count? I don't get anywhere near half a dozen. erserver, slony, dbmirror are off the top of my head for OSS ones ... then Command Prompt has their replication solution, so that's four ... wasn't there one out of russia? I can't recall the name of it though :( apparently someone is still working on pgreplication ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [ADMIN] Replication in main PostgreSQL codebase
Marc G. Fournier wrote: > On Tue, 6 Jul 2004, Peter Eisentraut wrote: > > > Marc G. Fournier wrote: > >> Christopher is correct ... if there was such a thing as an 'end all, > >> be all' replication solution, there wouldn't be a half a dozen > >> different ones out there ... > > > > Which ones are you thinking of in your count? I don't get anywhere near > > half a dozen. > > erserver, slony, dbmirror are off the top of my head for OSS ones ... then > Command Prompt has their replication solution, so that's four ... wasn't > there one out of russia? I can't recall the name of it though :( > apparently someone is still working on pgreplication ... And pgcluster, which does multi-master. -- 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 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[ADMIN] [admin] is there app to catalog email oe6
Hi I am hoping posgresql will get more widely used. I have an idea for an application. Consider , after spending months collecting email with information for research there becomes the need to catalog it and store it efficiently. A lot of it is scientific and engineering related. Is there an open source project to pull the outlook express email and catalog it into postgresql. and if not is there any interest in starting a project. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] [admin] is there app to catalog email oe6
On Tue, 6 Jul 2004 23:30:46 -0400, Paul Gimpelj <[EMAIL PROTECTED]> wrote: > I am hoping posgresql will get more widely used. Aren't we all? > I have an idea for an application... I'm not sure this is the most appropriate list for such a discussion. pgsql-admin is for discussions related to adminstering PostgreSQL. If you want to pursue such a project, you'd probably be well served by looking at the various tools that will convert Outlook's .pst files to standard *nix mbox files. From there, you're just parsing plain text, which any number of tools (even, like as not, some designed specifically for dumping mboxen into SQL tables) can work handily with. /rls -- :wq ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
