Re: [BUGS] Error compiling PostgreSQL 7.4 for Fedora Core 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 08 December 2003 9:33 pm, Tom Lane wrote: > In the absence of any brilliant insight, I'd suggest slogging through > Gen_fmgrtab.sh to try to narrow down where functions are getting lost > --- add code to save the various intermediate files, and see what's in > 'em. If we knew exactly which step was losing the functions it'd be a > leg up. > I just did this. I am no awk or sed expert. I can't see any faults in the script other than it is difficult to read. My only thought is that some of the regex behavior has changed, but I can't identify anything. The regexes used here are very standard. Unfortunately, in testing the bugger, it accidentally worked. I find this most disturbing. However, I was pleasantly surprised that it failed at least one more time before working properly. Chalk the cause of this bug up as high-energy particles striking the memory chip in just the right place at just the right time. The only other thing I think might affect it is the fact that I was simultaneously compiling PostgreSQL 7.3.4, reading email, and downloading stuff. Perhaps there is a strange race condition in the make process. Of course, the recent power outage in the area (that didn't affect us) might've been a cause as well. I apologize that I couldn't ease your pain, Tom. I know how it feels to see the same bug pop up occasionally, only to be solved by hitting the "Redo" key. - -- Jonathan Gardner [EMAIL PROTECTED] Live Free, Use Linux! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/1XQJWgwF3QvpWNwRAi0FAKCkPV+yn0y3kNT3AoHy5TX9a0v6NACaA7qI PlIJfFguW4LNr+4RL535rIM= =wWkP -END PGP SIGNATURE- ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Error compiling PostgreSQL 7.4 for Fedora Core 1
Tom Lane wrote: We could fall back in that direction if we had to. But I'd like to understand why we have to, first. Gen_fmgrtab.sh has worked on all our supported platforms for a long time, and I'm disinclined to assume that it's suddenly broken ... especially on what's presumably a modern platform. I'm having a real problem with the idea that Fedora incorporates a broken awk or sed. I was able to rebuild from source rpm on a Fedora machine without any problem, so I don't think it's a case of wholesale breakage. It's not my normal development machine, but I'll try compiling from source [...tries...] Yup, I got a clean build from source with the following configure line: ./configure \ --prefix=/usr/local/pgsql-7.4 \ --with-pgport=55434 \ --with-perl \ --with-tcl \ --with-tclconfig=/usr/lib \ --without-tk \ --with-python \ --enable-nls \ --enable-debug \ --enable-cassert \ --enable-depend \ --with-openssl \ --with-pam \ --enable-integer-datetimes \ --with-krb5=/usr/kerberos \ --with-includes=/usr/include/et/ The only adjustment from my RH9 box was the last line. Without it com_err.h wasn't being found. Joe ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] BUG #1003: postgres config error
The following bug has been logged online: Bug reference: 1003 Logged by: hemachandra Email address: [EMAIL PROTECTED] PostgreSQL version: 7.3 Operating system: Red Hat8.0 Description:postgres config error Details: I have installed the Postgres by the procedure by. it got installed at /usr/local/pgsql/bin but, when i re-start the system. the postgres service starts from /usr/bin. what shall i do i have tried it by editing the /etc/rc.d/inid.d / postgresql file. but no result regards hemu ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] BUG #1003: postgres config error
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > I have installed the Postgres by the procedure by. it got installed > at /usr/local/pgsql/bin but, when i re-start the system. the > postgres service starts from /usr/bin. > > what shall i do i have tried it by editing the > /etc/rc.d/inid.d / postgresql file. > but no result I really have no idea what this report is intended to mean. Can you please restate the problem? Bug reporting guidelines are here: http://www.postgresql.org/docs/current/static/bug-reporting.html -Neil ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Error compiling PostgreSQL 7.4 for Fedora Core 1
Jonathan Gardner <[EMAIL PROTECTED]> writes: > Unfortunately, in testing the bugger, it accidentally worked. I find this > most disturbing. However, I was pleasantly surprised that it failed at > least one more time before working properly. Weird; there's no obvious reason for the script to be nondeterministic. The only idea I can think of is that you were almost out of /tmp space and the missing data got lost because of lack of space to put it. I'm not sure whether awk/sed/etc would detect write failures on stdout. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] (ver. 7.4) select netmask('192.168.1.5/24') return '255.255.255.0/24' not '255.255.255.0' (example in docs)
(ver. 7.4) select netmask('192.168.1.5/24') return '255.255.255.0/24'
not '255.255.255.0' (example in docs)
(ver. 7.3) return '255.255.255.0'
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
[BUGS] postmaster.pid in version 7.4
My postmaster.pid is something like: 23479 /export/home1/staff/marini/pgsql/data 5432001 11703 I don't know if there is something wrong with my installation (I run postgresql on Ultra-2 station with Solaris 6), for sure I cannot stop postgrsql server using: kill `cat /usr/local/pgsql/data/postmaster.pid` as described in INSTALL file. The right stop command should be: kill `cat /usr/local/pgsql/data/postmaster.pid|head -1` Best regards Dario Marini ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] Unintended shutdown in postgres 7.4
Let me just say that I love all the work that has been done for postgres 7.4. The information_schema is totally cool! We've been seeing a problem where the database server will shutdown unexpectedly. This generally happens when we are in the middle of importing a large dump in .sql format from a mysql database (we're currently converting). Interesting things in the log file are: LOG: could not send data to client: Broken pipe LOG: unexpected EOF on client connection LOG: received fast shutdown request LOG: aborting any active transactions FATAL: terminating connection due to administrator command However, nobody issued a "fast shutdown request". It just seems like the DB died and stopped responding. Has anybody else seen this before? Do you need me to gather any more data on the problem? Thanks, Chad ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] decode function
Hi
I don't know if it is really a bug or a missuse of postgresql but when I issue the
following request
select decode(encode('µ'::bytea, 'escape'), 'escape');
, the result is \346, not 'µ'.
Any help or a forum link ?
Thanks in advance
Gerard.
PS: PostGreSQL 7.4, Red Hat 8, Base under SQL_ASCII or UNICODE (doesn't work either)
Les noms de domaine les moins chers du marché : 6,49 euros HT sur
http://www.lycos.fr/pro .
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
[BUGS] java.lang.NullPointerException - at org.postgresql.Connection.ExecSQL(Connection.java:312)
>Hi! > >We are experiencing problems on a live application and are getting intermittent >errors. The stack trace is as follows. As the system is live, this is urgent. > >java.lang.NullPointerException > at org.postgresql.Connection.ExecSQL(Connection.java:312) > at org.postgresql.jdbc2.Connection.setAutoCommit(Connection.java:141) > at > org.enhydra.jdbc.standard.StandardXADataSource.getFreeConnection(StandardXADataSource.java:392) > at > org.enhydra.jdbc.standard.StandardXAConnection.getConnection(StandardXAConnection.java:124) > at > org.enhydra.jdbc.pool.StandardPoolDataSource.getConnection(StandardPoolDataSource.java:186) > at > org.enhydra.jdbc.pool.StandardPoolDataSource.getConnection(StandardPoolDataSource.java:152) > at > com.mphasis.give.common.utilities.DatabaseUtil.getConnection(DatabaseUtil.java:46) > at com.mphasis.give.payment.CartDAO.addToCart(CartDAO.java:161)> >We are using JOTM.. Any help would be appreciated. Regards, Dhaval ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Failed regression test in postgresql-7.4
Thanks, Bruce. I have a 7.3.4 install in my current path when running the regression tests. I will try rebuilding and retesting with a modified path. Lane Hoy [EMAIL PROTECTED] On Sat, 6 Dec 2003, Bruce Momjian wrote: > [EMAIL PROTECTED] wrote: > > /usr/local/src/postgresql-7.4/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/createdb: > > relocation error: > > /usr/local/src/postgresql-7.4/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/createdb: > > undefined symbol: get_progname > pg_regress: createdb failed > make[2]: > > *** [check] Error 2 > > This error means that you have an old createdb in your path or have an > old libpq lying around. > > -- > 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 7: don't forget to increase your free space map settings
Re: [BUGS] decode function
gerard manvu wrote:
> I don't know if it is really a bug or a missuse of postgresql but
> when I issue the following request select decode(encode('µ'::bytea,
> 'escape'), 'escape');
> , the result is \346, not 'µ'.
That's the same thing. bytea stores bytes, not characters, so we expect
that you are primarily interested in the byte value.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [BUGS] java.lang.NullPointerException - at
On Mon, 8 Dec 2003, Dhaval Bhagat wrote: > >Hi! > > > >We are experiencing problems on a live application and are getting intermittent > >errors. The stack trace is as follows. As the system is live, this is urgent. > > > >java.lang.NullPointerException > > at org.postgresql.Connection.ExecSQL(Connection.java:312) > > at org.postgresql.jdbc2.Connection.setAutoCommit(Connection.java:141) > > at > > org.enhydra.jdbc.standard.StandardXADataSource.getFreeConnection(StandardXADataSource.java:392) > > at > > org.enhydra.jdbc.standard.StandardXAConnection.getConnection(StandardXAConnection.java:124) > > at > > org.enhydra.jdbc.pool.StandardPoolDataSource.getConnection(StandardPoolDataSource.java:186) > > at > > org.enhydra.jdbc.pool.StandardPoolDataSource.getConnection(StandardPoolDataSource.java:152) > > at > > com.mphasis.give.common.utilities.DatabaseUtil.getConnection(DatabaseUtil.java:46) > > at com.mphasis.give.payment.CartDAO.addToCart(CartDAO.java:161)> > > >We are using JOTM.. > You have not indicated what version of the JDBC driver you are using, but the fact that it has org.postgresql.Connection indicates that it is from the 7.2 series at the newest. Try upgrading to a newer version from http://jdbc.postgresql.org/download.html Kris Jurka ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] (ver. 7.4) select netmask('192.168.1.5/24') return '255.255.255.0/24'
saint wrote:
(ver. 7.4) select netmask('192.168.1.5/24') return '255.255.255.0/24'
not '255.255.255.0' (example in docs)
(ver. 7.3) return '255.255.255.0'
Fixed on 7.4.1
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 8: explain analyze is your friend
