Re: [ADMIN] Fatal error: Allowed memory size of 8388608 bytes exhausted

shreedhar wrote: I am using PHP4 as client side. [snip] Subject: Re: [ADMIN] Fatal error: Allowed memory size of 8388608 bytes exhausted this is a php appache message. either A) you have a phpscript that allocates memory in a infinate loop B) your php script has become so big, or its data

[ADMIN] multibytes language support

Hi, there, I installed postgresql 7.3.4 by RPMs, and created a database. Now I found I need multibytes language support. How can I change the database setting? I don't want to re-create the database. I installed JDBC and when some columns have multibytes chars. JDBC throws error. Please help

Re: [ADMIN] System Tables

well in unix man psql command line options -E shows the queries that are generated by the \d or other sudo commands reading a 10 point font on a 1600x1280 screen sucks, please text only to mailing lists -- Arno Karner aka Behind the Muffs West 7th St., St. Paul aka smell, Minn

Re: [ADMIN] Call to undefined function: pg_connect()

shreedhar wrote: Hi All, I Updated my Postgresql Server from 7.2.4 which came along with RH7.3 to 7.3.2. After updating I could not able to connect database through PHP. So I recompiled PHP4.1.2 (same version which have earlier in my system), even then I am not able to connect through

[ADMIN] pg_hba.conf ident sameuser

can this use the encrpted responses from pidentd? Tried search of the archives, but this wasn't helpful thanks Arno ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's

[ADMIN] fyi error follow up

there was a cron job running doing a vacum on the entire database ---(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: [ADMIN] fyi error follow up

Tom Lane wrote: maillist [EMAIL PROTECTED] writes: there was a cron job running doing a vacum on the entire database I was about to say that then it's a known issue --- two ANALYZE operations running concurrently for the same table can generate a simple_heap_insert or simple_heap_update

Re: [ADMIN] fyi

Stephan Szabo wrote: On Thu, 31 Jul 2003, maillist wrote: select * from apps where (not apppag = null); returns nothing when it should return every thing No. It should return nothing. apppag = null returns unknown for every row. Use IS NULL to test if a value is null. hmmm now i'm

[ADMIN] fyi regarding error I've seen posted before

Database error:Invalid SQL: VACUUM VERBOSE ANALYZE ids_logs PostgreSQL Error: 1 (ERROR: simple_heap_delete: tuple concurrently updated ) aged deleted 28954 records I got these error messages from my php script that processes system logs from my linux / unix boxes. this is the first time I've seen

Re: [ADMIN] fyi regarding error I've seen posted before

Tom Lane wrote: maillist [EMAIL PROTECTED] writes: Database error:Invalid SQL: VACUUM VERBOSE ANALYZE ids_logs PostgreSQL Error: 1 (ERROR: simple_heap_delete: tuple concurrently updated ) Is it possible that you had another VACUUM ANALYZE running concurrently on this same table

[ADMIN] time zone on timestamp fields

Ok me dumb, I've spend copple days editing my table definintions from Dlm DATETIME NOT NULL DEFAULT TEXT 'now' Dlm = date time last modified to Dlm timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP which from my previous post I was told should be Dlm timestamptz NOT NULL DEFAULT

[ADMIN] fyi

previous table definition guess no not null of default '' curreent table definitionCREATE TABLE apps ( Id int not null unique,-- AppId Sym varchar(8) not null default '', -- app symbol name Nam varchar(30) not null default '',-- app full name BitPriv varchar(10) not null