[GENERAL] compile error

hi, when i run ./configure on winnt, can't continue to compile, error messages in error.txt attached, can help me to resolve this problem? I used cygwin b2.0. winnt workstation 4.0. c:\postgresql-6.5.1 <> thanks a lot. sincerely sun loading cache ./config.cache checking host system type...

[GENERAL] Backend crashed with status 139 ( may be long SQL query)

Hello all. When i had tried to insert into text field text (length about 4000 chars), the backend have crashed with status 139. This error is happened when the query length ( SQL query) is more than 4095 chars. I am using PostgreSQL 6.4.2 on Linux. My questions are: 1. Is there problem with te

Re: [GENERAL] JDBC

On Sat, 7 Aug 1999 [EMAIL PROTECTED] wrote: > Does anyone know of a source for some sample code for using jdbc or an > online tutorial? There's an entire directory of examples included with the source code. Peter -- Peter T Mount [EMAIL PROTECTED] Main Homepage: http://www.retep.o

[GENERAL] Need beta testers for Java report writer for Postgresql

I've written a menu-driven report writer in Java for Postgresql and need 3 or 4 beta test volunteers for the first run of testing. Once it's completed I intend to release it for general use in some version of GPL so you'll be getting an early look at something you might want to use later

[GENERAL] Newbie - Inserting Images

This message was sent from Geocrawler.com by "Robert Castley" <[EMAIL PROTECTED]> Be sure to reply to that address. Can any one give me some step by step instructions for storing images in a PostgreSQL Database. I am correct in understanding from these lists, I need to use a program rather than

[GENERAL] Limit postgresql query results

Hello, I am using PostgreSQL 6.3 and PHP. I am trying to build a query that only returns 20 results at a time, with a "next" link at the bottom of the query results for the next 20. Someone suggested to me that I use the below block of code (pg_Exec ($conn, "set QUERY_LIMIT='20'");). How would I u

[GENERAL] FATAL 1: my bits moved right off the end of the world!

When I try to CREATE a FUNCTION I got this message in the debug log : FATAL 1: my bits moved right off the end of the world! Any advice? TIA Roberto -- Roberto Moreda Resp. Dpto. Informática Handem/San Luis Tlf +34 981 779000 Fax +34 981 779022 Pol. Piadela Sur, Autovía A6 Sal.567

Re: [GENERAL] FATAL 1: my bits moved right off the end of the world!

[Charset iso-8859-1 unsupported, filtering to ASCII...] > When I try to CREATE a FUNCTION I got this message in the debug log : > > FATAL 1: my bits moved right off the end of the world! > > Any advice? One of my favorite PostgreSQL error messages. Other than that, I don't know. Do other peo

Re: [GENERAL] [Fwd: Maximum filesize of one file]

Dear CN, Yes, thanks for you message. I am well aware of the 32 bit=2GB limitation in the ext2fs. Currently, pgsql 6.5.x breaks up the files containing tables into roughly 1 GB chunks. My question is: will pgsql do the same for the files containing the indices? Correction to info in my previ

Re: [GENERAL] [Fwd: Maximum filesize of one file]

> Dear CN, > > Yes, thanks for you message. I am well aware of the > 32 bit=2GB limitation in the ext2fs. > > Currently, pgsql 6.5.x breaks up the files containing > tables into roughly 1 GB chunks. My question is: will > pgsql do the same for the files containing the indices? > > Correction

[GENERAL] Error: index of catalog table

I got a new problem :) sanluis=> vacuum verbose pg_proc; NOTICE: --Relation pg_proc-- NOTICE: Pages 43: Changed 0, Reapped 24, Empty 1, New 0; Tup 946: Vac 94, Crash 28, UnUsed 0, MinLen 155, MaxLen 205; Re-using: Free/Avail. Space 191464/0; EndEmpty/Avail. Pages 23/0. Elapsed 0/0 sec. ERROR:

Re: [GENERAL] [Fwd: Maximum filesize of one file]

On Mon, 16 Aug 1999, Martin Weinberg wrote: > Currently, pgsql 6.5.x breaks up the files containing > tables into roughly 1 GB chunks. My question is: will > pgsql do the same for the files containing the indices? It should do, as it's the StorageManager that does the splitting, and tables/ind

[GENERAL] XA 2 phase

I was sent this mail, and not sure how to reply to it... > In transaction processing, a two-phase commit guarantees that synchronous > transactions across multiple datasources will meet the ACID properties: > atomic, consistent, isolated, durable. The protocol was standardized by the > XA group.

Re: [GENERAL] v6.5 foreign key trigger reposted with details

amy cheng wrote: > > >1. all applications should use BEGIN/END; > B) what does that mean for perl? or just limited to PL/pgSQL-- > then, isn't BEGIN/END the common syntax in PL/pgSQL? > > C) can you give me an outline of PL/pgSQL for 2. and 3. ? > >2. in first transaction (deleting/updating