Re: [HACKERS] [BUGS] PostgreSQL client has problems when libbind is

it working. ----- -- Palle Girgensohn wrote: Was this problem fixed? Can I request the problem report @ FreeBSD to be closed? Thanks, Palle --On torsdag, juni 12, 2003 18.51.18 -0400 "Yves R. Crevecoeur" <[EMAIL PROTECTED]> wrote: > Don't break BeOS suppo

Re: [BUGS] PostgreSQL client has problems when libbind is installed

ww.yellowtab.com http://www.yellowtab.com/board/ http://www.yellowtab.com/support/ Regards, Yves - Original Message - From: "Tom Lane" <[EMAIL PROTECTED]> To: "Palle Girgensohn" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; "Tom Alsberg" <[EMAI

Re: [BUGS] Bug #926: if old postgresql.jar in CLASSPATH, ant fails

wrote: Palle Girgensohn ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description if old postgresql.jar in CLASSPATH, ant fails Long Description See http://www.freebsd.org/cgi/query-pr.cgi?pr=48878 If there is an older postgresql.jar file i

[BUGS] PostgreSQL client has problems when libbind is installed

Hi! This was reported to the FreeBSD bug report system. Under special cirumstances, building postgresql fails. Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/47218 This sounds like a bug in the build process to me. I cannot confirm though. Please check with the original author. /

Re: [BUGS] select a.name ... union select a.name ... order by a.name fails in 7.1

Tom, thanks for your input. Now I have something to bash my programmers over the head with ;-) No, just kidding... But as you say, it is plain bad SQL, I realize this fully now. Oddly enough, I have a SQL book that has one or two examples with order by a.foobar. Oh well... Thanks for the prompt

[BUGS] select a.name ... union select a.name ... order by a.name fails in 7.1

Hi! I'm not certain this is correct SQL, and I know the rewrite is easy, but here is a difference I found between 7.0.3 and 7.1: select a.name from users a union select a.name from oldusers a order by a.userid; ERROR: Relation 'a' does not exist This works fine in postgres 7.0.x the simple

Re: [BUGS] The Data Base System is in recovery mode

Tom Lane <[EMAIL PROTECTED]> writes: > and GetTemplateEncoding is just about as SEGV-proof as any routine > I've ever seen: > > static inttemplateEncoding; > ... > int > GetTemplateEncoding() > { > return (templateEncoding); > } Heh > I speculate that you gave gdb the wrong executabl

Re: [BUGS] The Data Base System is in recovery mode

ores DEBUG: Data Base System is starting up at Wed Oct 18 14:51:53 2000 DEBUG: Data Base System was interrupted being in production at Wed Oct 18 14:51:21 2000 DEBUG: Data Base System is in production state at Wed Oct 18 14:51:53 2000 Hope this helps... /Palle Tom Lane <[EMAIL

Re: [BUGS] The Data Base System is in recovery mode

Tom Lane <[EMAIL PROTECTED]> writes: > Palle Girgensohn <[EMAIL PROTECTED]> writes: > Oh, gee. sorry! I slipped with the mouse when cut'n'pasting. The > first > statement should be a create view. The view is dropped and > created > "on-the

Re: [BUGS] The Data Base System is in recovery mode

Tom Lane <[EMAIL PROTECTED]> writes: > Palle Girgensohn <[EMAIL PROTECTED]> writes: > > New facts: The problem "moved" when raising the -B from default (64) > > to 1000 (-N 100 now). Now, here's what happens: > > Interesting. I am also using -o

Re: [BUGS] The Data Base System is in recovery mode

; text, "postadress" text, "land" character(2) DEFAULT 'SE' NOT NULL, "telefon" text, "telefax" text, "mobil" text, "email" text, "privemail" text, "url&q

[BUGS] The Data Base System is in recovery mode

Hi! I have a problem with postgresl-7.0.2 on Freebsd 4-stable. Somehow, shared memory gets corrupted by a certain type of query, and all databases end up unusable until I kill -9 the bad postgres process and stop+restart postgres. I mistakenly ran postgres without -N and -B flags, and I guess

[BUGS] reproducable command sequence to get "mdopen: Couldn't open..."

Hi! I have seen this problem on several occasions, using 7.02: # vacuum; NOTICE: mdopen: couldn't open at_provider_user_info: No such file or directory NOTICE: RelationIdBuildRelation: smgropen(at_provider_user_info): No such file or directory NOTICE: mdopen: couldn't open at_provider_user_i