Re: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
OK, here's a situation. One of the programmers at your company runs the disk out of space. You're going to go bonk him on the head, but first, there are more pressing matters. PostgreSQL 6.5 has horked up the tables, and needs to be fixed. 7.0 is released, which has a fix for the problem. Let's be real here. If your system is out of disk space, you can't do a dump to put it into 7.0. You're definitely gonna need 6.5 to work at this point... I know. And I was being real. That is the situation that happend at my company, and it also came up from at least one other person on the list. Yes, I needed 6.5 to get the data out. However, you *couldn't* dump the data, PSQL had horked the tables up too badly. I ended up writing a Perl script to get things from the tables, and put them into a flat file of SQL statements. It was ugly, but the clock was ticking. ; ) (nothing like a junior programmer doing a recursive grep of a large file system, and redirecting the results to a file *in* the filesystem he's grepping) Your problems aren't with RPM's, your problems the FHS. Distrib packages (RPM *or* DEB) will put stuff in FHS compliant locations, packages by anyone else will put files where they want. If you feel that's incorrect, Irespectfully suggest you hit up the LSB/FHS people if you want that to change, NOT Red Hat, PostGreSQL, or anyone else. I think you're missing the subtlety of my point, but that's fine. You're correct that this isn't the list, I'm going to drop the topic. steve
RE: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
The last thing that a system admin needs when upgrading PostgreSQL is "Oh, crap, I forgot to uninstall the RPM of the old one first." If you're switching from RPM to compiling source, that's your own damn fault. If you're upgrading (rpm -U) then that isn't a concern, as it does it for you. Rob Nelson [EMAIL PROTECTED]
Re: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
The last thing that a system admin needs when upgrading PostgreSQL is "Oh, crap, I forgot to uninstall the RPM of the old one first." Then upgrade the RPM's. It isn't hard. OK, here's a situation. One of the programmers at your company runs the disk out of space. You're going to go bonk him on the head, but first, there are more pressing matters. PostgreSQL 6.5 has horked up the tables, and needs to be fixed. 7.0 is released, which has a fix for the problem. Are you going to sit around waiting for RPM's, while your tables are all horked up, and the programming department is breathing down your neck because they can't get work done? If you're going to install from source on a RedHat machine, it is simply prudent practice, regardless of the package, to make sure the RPM version is not already installed. I agree. And, the fact of the matter is that there are likely far more PostgreSQL installations from RPM than from source. I fail to see the relevance of that argument. Popularity does not make correctness. If I'm just being extremely dense about that sentence, feel free to let me know. steve
RE: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
Hmm so, if the local administrator wants to compile the source, it should go in /usr/local. If he wants to use a package manager, it should go somewhere else? Seems either pedantic or silly to me. Perhaps, but such is how the FHS came out. FWIW, SCO (what I work on daily) seems to respect this designation as well. Rob Nelson [EMAIL PROTECTED]
Re: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
Steve Wolfe wrote: Then upgrade the RPM's. It isn't hard. OK, here's a situation. One of the programmers at your company runs the disk out of space. You're going to go bonk him on the head, but first, there are more pressing matters. PostgreSQL 6.5 has horked up the tables, and needs to be fixed. 7.0 is released, which has a fix for the problem. Not a good example, but I understand your comparison. Are you going to sit around waiting for RPM's, while your tables are all horked up, and the programming department is breathing down your neck because they can't get work done? Actually, since I'm the RPM maintainer, I'll build a set for the new version (which I would have been tracking since the first beta) the hour it is released. That is if I'm online when the release occurs. But, then again, I'll have already built RPM's for the beta releases. It's this very problem that got me in this business of maintaining the RPM's in the first place over a year ago. Scratch that itch. If you're going to install from source on a RedHat machine, it is simply prudent practice, regardless of the package, to make sure the RPM version is not already installed. I agree. And, the fact of the matter is that there are likely far more PostgreSQL installations from RPM than from source. I fail to see the relevance of that argument. Popularity does not make correctness. If I'm just being extremely dense about that sentence, feel free to let me know. The relevance is that most who use it don't really care where the stuff is. They just want to upgrade. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Re: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
Did you have those two dependency packages installed? I know, silly
question, but...
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
- Original Message -
From: "Darrin Ladd" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 24, 2000 1:14 AM
Subject: [GENERAL] Postgres 7.0.2-2 on Red Hat 7.0?
Howdy!
I was wondering if anyone has installed the postgres 7.0.2-2 on Red Hat 7.0?
I have Red Hat running on a box with an AMD processor (K62). I used to have
6.5.3 installed on the same box, but running Red Hat 6.2 and it worked
great! But now, I am having serious difficulties with the installation of
7.0.2-2. I tried installing the binary rpm's (i386) and I got this error:
Error: Failed dependencies:
libncurses.so.4 is needed by postgresql-7.0.2-2
libreadline.so.3 is needed by postgresql-7.0.2-2
I successfully uninstalled 6.5.3, so I am pretty sure that it isn't picking
up old versions. So then I tried compiling the source for 7.0.2 and got
this error:
gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -Wmissi
ng-declarations -I.. -c -o
comment.o comment.c
gcc -I../../include -I../../backend -O2 -Wall -Wmissing-prototypes -Wmissi
ng-declarations -I.. -c -o copy.o
copy.c
copy.c: In function `CopyFrom':
copy.c:1019: Insn does not satisfy its constraints:
(insn 89 2735 92 (set (mem:HI (plus:SI (reg:SI 6 ebp)
(const_int -52 [0xffcc])) 0)
(mem/s:HI (mem:SI (plus:SI (reg:SI 6 ebp)
(const_int -144 [0xff70])) 0) 8)) 36 {*movhi_1}
(nil) (nil))
copy.c:1019: Internal compiler error in reload_cse_simplify_operands, at
reload1.c:8110
Please submit a full bug report.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
make[2]: *** [copy.o] Error 1
make[2]: Leaving directory
`/usr/src/redhat/SOURCES/postgresql-7.0.2/src/backend/commands'
make[1]: *** [commands.dir] Error 2
make[1]: Leaving directory
`/usr/src/redhat/SOURCES/postgresql-7.0.2/src/backend
'
make: *** [all] Error 2
Now, I am pretty sure that this isn't good. So, I was wondering if this was
a problem with Red Hat 7.0 or with the way I have setup my system.
If you have any suggestions, I would be greatly appreciative.
Thanks!
Darrin
