Re: [PATCHES] ecpg compile (compatlib)

2003-06-24 Thread Jason Tishler
Bruce,

On Tue, Jun 24, 2003 at 09:33:56AM -0400, Bruce Momjian wrote:
 My last question is do we have this covered in every other case except
 this ecpg one?

AFAICT, yes.  Or, more accurately, with CVS updated at about 7:00 AM ET
today, the following built cleanly (with deststar's ecpg patch applied
locally):

configure --enable-multibyte --with-python --with-perl --with-java --with-CXX ...

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

---(end of broadcast)---
TIP 8: explain analyze is your friend


Re: [PATCHES] ecpg compile (compatlib)

2003-06-24 Thread Bruce Momjian

OK, ecpg patch applied.  Thanks for the testing.

---

Jason Tishler wrote:
 Bruce,
 
 On Tue, Jun 24, 2003 at 09:33:56AM -0400, Bruce Momjian wrote:
  My last question is do we have this covered in every other case except
  this ecpg one?
 
 AFAICT, yes.  Or, more accurately, with CVS updated at about 7:00 AM ET
 today, the following built cleanly (with deststar's ecpg patch applied
 locally):
 
 configure --enable-multibyte --with-python --with-perl --with-java --with-CXX ...
 
 Jason
 
 -- 
 PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
 Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6
 

-- 
  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 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html


[PATCHES] Interval Patch

2003-06-24 Thread Larry Rosenman
This is against 7.3.3 sources, but it fixes the TODO
* Have SELECT '13 minutes'::interval display zero seconds in ISO
  datestyle
*** datetime.c.orig Sat May  3 23:30:35 2003
--- datetime.c  Tue Jun 24 15:54:39 2003
***
*** 3498,3504 
is_nonzero = TRUE;
}
/* otherwise, integer seconds only? */
!   else if (tm-tm_sec != 0)
{
sprintf(cp, :%02d, abs(tm-tm_sec));
cp += strlen(cp);
--- 3498,3504 
is_nonzero = TRUE;
}
/* otherwise, integer seconds only? */
!   else
{
sprintf(cp, :%02d, abs(tm-tm_sec));
cp += strlen(cp);
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749



datetime.patch
Description: Binary data

---(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


Re: [PATCHES] perform.sgml update

2003-06-24 Thread Bruce Momjian

Patch applied.  Thanks.

---


Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
 
[ PGP not available, raw data follows ]
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 NotDashEscaped: You need GnuPG to verify this message
 
 
 Small patch to link to the proper place in the runtime file, 
 and to add the schemaname column to the description of the 
 pg_stats view.
 
 
 --
 Greg Sabino Mullane [EMAIL PROTECTED]
 PGP Key: 0x14964AC8 200306111031
 
 
 
 Index: perform.sgml
 ===
 RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/perform.sgml,v
 retrieving revision 1.28
 diff -c -r1.28 perform.sgml
 *** perform.sgml  25 Mar 2003 16:15:37 -  1.28
 --- perform.sgml  11 Jun 2003 14:22:02 -
 ***
 *** 66,72 
   estimates are converted into disk-page units using some
   fairly arbitrary fudge factors. If you want to experiment with these
   factors, see the list of run-time configuration parameters in
 ! xref linkend=runtime-config.)
  /para
   
  para
 --- 66,72 
   estimates are converted into disk-page units using some
   fairly arbitrary fudge factors. If you want to experiment with these
   factors, see the list of run-time configuration parameters in
 ! xref linkend=runtime-config-optimizer.)
  /para
   
  para
 ***
 *** 435,440 
 --- 435,446 
   /thead
   
   tbody
 +  row
 +   entryliteralschemaname/literal/entry
 +   entrytypename/type/entry
 +   entryName of the schema containing the table./entry
 +  /row
 + 
row
 entryliteraltablename/literal/entry
 entrytypename/type/entry
 
 
 
 
 
 -BEGIN PGP SIGNATURE-
 Comment: http://www.turnstep.com/pgp.html
 
 iD8DBQE+5z3ovJuQZxSWSsgRAlIhAJ4mOgsrKa1xQXiMxTWWawPsGrnPjgCg3BLs
 fw61yiB/4rfQotCO4MIvI4Y=
 =YoCD
 -END PGP SIGNATURE-
 
 
 ---(end of broadcast)---
 TIP 5: Have you checked our extensive FAQ?
 
 http://www.postgresql.org/docs/faqs/FAQ.html
 
[ Decrypting message... End of raw data. ]

-- 
  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 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])


Re: [PATCHES] array support patch phase 1 patch

2003-06-24 Thread Joe Conway
Bruce Momjian wrote:
Patch applied.  Joe, I need some text about this patch for the release
notes.  It has so much stuff in it I don't know how to describe it.
OK -- I'll send you something. I need to finish the documentation also, 
so I'll send both at once.

Joe



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [PATCHES] Runtime.SGML diff ... please expedite!

2003-06-24 Thread Bruce Momjian

Patch applied.  Thanks.

---


Rod Taylor wrote:
-- Start of PGP signed section.
 This is the other portion he is referring to.
 
 client-auth.sgml references a renamed ID in runtime.sgml
 
 On Wed, 2003-06-18 at 16:46, Tom Lane wrote:
  Josh Berkus [EMAIL PROTECTED] writes:
   Attached is the fully corrected version of the re-ording patch for=20
   Runtime.sgml and dependant files.
  
  Dependent files?  I only see a diff for runtime.sgml there ...
  
  regards, tom lane
  
  ---(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
 -- 
 Rod Taylor [EMAIL PROTECTED]
 
 PGP Key: http://www.rbt.ca/rbtpub.asc

[ Attachment, skipping... ]
-- End of PGP section, PGP failed!

-- 
  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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [PATCHES] [NOVICE] connectby() minor bug in errormessage

2003-06-24 Thread Joe Conway
Nabil Sayegh wrote:
validateConnectbyTupleDesc

When the fourth column (tupdesc-attrs[3]) fails the type check, the
errormessage should be fourth column must be... and not third column
must be ...
line 1372
http://www.joeconway.com/tablefunc.tar.gz
Attached is a patch for the issue reported above by Nabil. Please apply.

Thanks,

Joe

Index: contrib/tablefunc/tablefunc.c
===
RCS file: /opt/src/cvs/pgsql-server/contrib/tablefunc/tablefunc.c,v
retrieving revision 1.18
diff -c -r1.18 tablefunc.c
*** contrib/tablefunc/tablefunc.c   15 Jun 2003 17:59:09 -  1.18
--- contrib/tablefunc/tablefunc.c   25 Jun 2003 02:46:11 -
***
*** 1369,1375 
/* check that the type of the forth column is TEXT if applicable */
if (show_branch  tupdesc-attrs[3]-atttypid != TEXTOID)
elog(ERROR, Query-specified return tuple not valid for Connectby: 
!third column must be type %s, format_type_be(TEXTOID));
  
/* OK, the tupdesc is valid for our purposes */
  }
--- 1369,1375 
/* check that the type of the forth column is TEXT if applicable */
if (show_branch  tupdesc-attrs[3]-atttypid != TEXTOID)
elog(ERROR, Query-specified return tuple not valid for Connectby: 
!forth column must be type %s, format_type_be(TEXTOID));
  
/* OK, the tupdesc is valid for our purposes */
  }

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html