Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Wed Oct 5 07:24:44 EDT 2005
+ Last updated: Fri Nov 4 20:35:04 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
1.7) What is the latest release?
- The latest release of PostgreSQL is version 8.0.4.
+ The latest release of PostgreSQL is version 8.1.
We plan to have a major release every year, with minor releases every
few months.
From: Zeugswetter Andreas <ZeugswetterA@spardat.at>
-$Date: 2005/10/26 13:20:47 $
+$Date: 2005/11/05 01:36:41 $
On AIX 4.3.2 PostgreSQL compiled with the native IBM compiler xlc
(vac.C 5.0.1) passes all regression tests. Other versions of OS and
Last modified date 2005-09-06
If you upgrade to maintenance level 5300-03, that will include this
-fix. Use the command "oslevel -r" to determine what maintenance level
+fix. Use the command "oslevel -r" to determine what maintenance level
you are at.
---
From: Christopher Browne <cbbrowne@ca.afilias.info>
http://www.faqs.org/faqs/aix-faq/part4/section-22.html
http://www.han.de/~jum/aix/ldd.c
+---
+From: Christopher Browne <cbbrowne@ca.afilias.info>
+Date: 2005-11-02
+
+On AIX 5.3 ML3 (e.g. maintenance level 5300-03), there is some problem
+with the handling of the pointer to memcpy. It is speculated that
+this relates to some linker bug that may have been introduced between
+5300-02 and 5300-03, but we have so far been unable to track down the
+cause.
+
+At any rate, the following patch, which "unwraps" the function
+reference, has been observed to allow PG 8.1 pre-releases to pass
+regression tests.
+
+The same behaviour (albeit with varying underlying functions to
+"blame") has been observed when compiling with either GCC 4.0 or IBM
+XLC.
+
+------------ per Seneca Cunningham -------------------
+
+The following patch works on the AIX 5.3 ML3 box here and didn't cause
+any problems with postgres on the x86 desktop. It's just a cleaner
+version of what I tried earlier.
+
+*** dynahash.c.orig Tue Nov 1 19:41:42 2005
+--- dynahash.c Tue Nov 1 20:30:33 2005
+***************
+*** 670,676 ****
+
+
+ /* copy key into record */
+ currBucket->hashvalue = hashvalue;
+! hashp->keycopy(ELEMENTKEY(currBucket), keyPtr, keysize);
+
+
+ /* caller is expected to fill the data field on return */
+
+
+--- 670,687 ----
+
+
+ /* copy key into record */
+ currBucket->hashvalue = hashvalue;
+! if (hashp->keycopy == memcpy)
+! {
+! memcpy(ELEMENTKEY(currBucket), keyPtr, keysize);
+! }
+! else if (hashp->keycopy == strncpy)
+! {
+! strncpy(ELEMENTKEY(currBucket), keyPtr, keysize);
+! }
+! else
+! {
+! hashp->keycopy(ELEMENTKEY(currBucket), keyPtr, keysize);
+! }
+
+
+ /* caller is expected to fill the data field on return */
+
+------------ per Seneca Cunningham -------------------
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Mon Sep 19 21:28:08 EDT 2005
+ Last updated: Thu Oct 27 09:48:14 EDT 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
If the postmaster is running, start psql in one window, then find the
PID of the postgres process used by psql using SELECT
pg_backend_pid(). Use a debugger to attach to the postgres PID. You
- can set breakpoints in the debugger and issue queries from psql. If
- you are debugging postgres startup, you can set PGOPTIONS="-W n", then
- start psql. This will cause startup to delay for n seconds so you can
- attach to the process with the debugger, set any breakpoints, and
- continue through the startup sequence.
+ can set breakpoints in the debugger and issue queries from the other.
+ If you are looking to find the location that is generating an error or
+ log message, set a breakpoint at errfinish. psql. If you are debugging
+ postgres startup, you can set PGOPTIONS="-W n", then start psql. This
+ will cause startup to delay for n seconds so you can attach to the
+ process with the debugger, set any breakpoints, and continue through
+ the startup sequence.
You can also compile with profiling to see what functions are taking
execution time. The backend profile files will be deposited in the
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
- <P>Last updated: Wed Oct 5 07:24:44 EDT 2005</P>
+ <P>Last updated: Fri Nov 4 20:35:04 EST 2005</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
<H3><A name="1.7">1.7</A>) What is the latest release?</H3>
- <P>The latest release of PostgreSQL is version 8.0.4.</P>
+ <P>The latest release of PostgreSQL is version 8.1.</P>
<P>We plan to have a major release every year, with minor releases
every few months.</P>
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
- <P>Last updated: Mon Sep 19 21:28:08 EDT 2005</P>
+ <P>Last updated: Thu Oct 27 09:48:14 EDT 2005</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
window, then find the <SMALL>PID</SMALL> of the <I>postgres</I>
process used by <I>psql</I> using <CODE>SELECT pg_backend_pid()</CODE>.
Use a debugger to attach to the <I>postgres</I> <SMALL>PID</SMALL>.
- You can set breakpoints in the debugger and issue queries from
+ You can set breakpoints in the debugger and issue queries from the
+ other. If you are looking to find the location that is generating
+ an error or log message, set a breakpoint at <I>errfinish</>.
<I>psql</I>. If you are debugging <I>postgres</I> startup, you can
set PGOPTIONS="-W n", then start <I>psql</I>. This will cause startup
projects / thirdparty / postgresql.git / commitdiff
