you DO have data you want to keep, you need to reinstall the old version,
dump its data, remove the old/install the new, blow out the directory, start
the new, and restore your data.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC
ourage people to keep using
> such old releases. If they are installing on a new machine they should
> update to something newer and less buggy.
We need the older versions to be compilable on newer systems to ease in
version upgrades and migration.
--
Lamar Owen
Director of Information
On Friday 19 December 2003 04:11 pm, Kris Jurka wrote:
> On Fri, 19 Dec 2003, Lamar Owen wrote:
> > On Friday 19 December 2003 01:27 pm, Kris Jurka wrote:
> > > The RPMs do not have the correct jar file. Try one of those available
> > > from http://jdbc.postgresql.or
the 7.3 jars and packaged those. The 7.4.1 packages
will have the 7.4 jars since they are now available.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu
---(
x27;postgresql.conf'.
Find the line '#tcpip_socket = false'
Change to 'tcpip_socket = true'
Notice that the # is gone.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
ontrib-7.1.2-5PGDG
> libreadline.so.4.1 is needed by postgresql-contrib-7.1.2-5PGDG
> libssl.so.1 is needed by postgresql-contrib-7.1.2-5PGDG
You need to install all of these on one line. You also need to get OpenSSL
and readline installed.
--
Lamar Owen
WGCR Intern
is.
Tom, Bruce: who has the python interface these days?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
t used to work right let me check.
> I attach both patch ( I added also the stop_immediate )
Many thanks.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an approp
no
checking for int64... no
checking for uint64... no
The only difference is the long long int is 64 bits here.
So, Tom, what's up with that?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 2: you
_INT 8
#define ALIGNOF_DOUBLE 8
#define MAXIMUM_ALIGNOF 8
This was built with the RPM spec file using the 'sparc32' utility that builds
the sun4 32bit userland executables.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)-
corrupt RPM will fail the installation. It
sounds to me like your RPM installation got hosed either due to a hardware
fault or running out of disk space on the /var partition. I certainly
reserve the right to be wrong; but to test this theory run 'rpm --rebuilddb
onnections to port 5432. UDP on port 5432 is not necessary.
This is, again, a security feature, and is intentional behavior. See
/usr/shar/doc/postgresql-7.1.3/README.rpm-dist for more information.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-
ules.
Red Hat 7.2 comes with PostgreSQL 7.1.3. And, as Stephan has already said,
this is intentional behavior. Edit postgresql.conf as he suggests, and port
5432 will show in the portscan.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadc
r, unless one comes standard with Red Hat 6.0.
> One does, I believe. I still think you are invoking the wrong copy of
> initdb, probably because the old one is first on your PATH.
> Try "which initdb".
RH 6.0 shipped with PostgreSQL 6.4.2. An 'rpm -qa|grep postgresql'
l phase fails every time I build an RPMset -- the RPM
spec file has to go through some steps to make it work.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
arl DeBisschop on the HACKERS list
for a patch to the spec file for the _perl_ package; you'll need to rebuild
it FIRST, then you canbuild pl/perl.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
he initscript, and it will happily create a new,empty, database
tree for you that you can start working with.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
"Editable" portion of the
> script which would turn this on or off, or at least a set of
> parameters to pass to postmaster.
See the file postgresql.conf in the database directory.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)-
etails of
your system configuration would be helpful.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
ch.
D'Arcy, can you take a look at what the RPM does and tell me how far off
the mark I am, as I am not a Python user? If you want the exact
incantationsI'm using to build the client, I can provide that
information.
But, the source code is the same.
--
Lamar Owen
WGCR Internet Radio
1 P
b, and start postmaster.
You seem to not have seen the same temp test failure I am seeing. Interesting.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
LC_ALL=C. Or simply delete it and reboot.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
's have this fixed, IIRC. Well, I _know_ the 7.1beta RPM's have it
fixed.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Tom Lane wrote:
>
> [EMAIL PROTECTED] writes:
> > initdb on Alpha dies with spinlock errors
>
> Make sure it's compiled -O0.
>
> We're hoping to clean up the Alpha portability problems for 7.1,
> but 7.0.* won't work very well on Alpha without -O0 :-
thil wrote:
>
> when I try to install the binary RPM for redhat 6.x,
> the first rpm (postgresql-7*) say "dependencies error : libpq.so need".
Install -devel along with it. I am updating the distributed RPM's now
to take care of this embarrassing typo.
--
Lamar Owen
WGC
tart with a fresh tarball extraction, pre-configure,
then apply the patches according to Ryan's instructions.
The RPMset does this automatically if you are building on an alpha.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Anyone remember
> something like that?
/etc/sysconfig/i18n is the file in question. A cold 6.2 install has the
file (as does 7.0) -- and upgrade from prior to 6.2 does not. The
collation with the file is different than without.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
> I am using PostgreSQL 7.0.2 on Yellow Dog Linux CS 1.2,
> I use the official RPMs.
There are known problems with the _official_ RPM's on PPC.
Specifically, they are compiled with an optimization setting too high.
Look for 7.0.3 PPC RPM's soon.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
the old RPM's, and then installing the new.
Are you running RedHat 6.x? RedHat 6.0 shipped PostgreSQL 6.4.2, RH 6.1
shipped 6.5.2, and 6.2 shipped 6.5.3. RedHat 7 shipped 7.0.2. RedHat
5.2 was the last RedHat release that shipped 6.3.2.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
7;s.
Also, Mandrake typically builds for Pentium and higher -- you may have a
CPU compatibility issue. Mandrake recompiles all their stuff -- but it
is typically compiled at a higher optimization level than RedHat's
stuff, as well as being compiled with a different compiler (at least in
the past)
sql with a 7.0 server...
Or a from-source 7.0 installation alongside a 6.5.3 RPM install, which
he needs to rpm -e if he wants to use the from-source build. Or he can
upgrade to the 7.0.2 RPM.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
nds like the optimization problem we have had for the PPC RPM's. I'm
pulling those until we can get that worked out.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
on a client's database (again, inside a
transaction so I could easily roll back the delete :-)).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
[EMAIL PROTECTED] wrote:
> A check in the rpm database showed that these python modules are installed:
> python-1.5.2-13
> pythonlib-1.23-1
> rpm-python-3.0.4-0.48
> So, what gives?
You need to have python-devel installed.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
es things.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
u have installed.
I'm copying Murray Todd Williams on this, as he did the binary rebuild
of my source RPM for PowerPC. It is possible that his machine's
$RPM_OPT_FLAGS is set to an excessively high optimization for PostgreSQL
7.0. If this is the case, I'll need to coordinate with
e then (about a year ago).
>
> The intention was to merge the changes back into Byrons stuff but that has not
> happened (that I am aware of).
Is the unixODBC driver GPL? If so, that's why it hasn't been pulled
back into the BSD-licensed PostgreSQL distribution.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
37 matches
Mail list logo
