Re: [BUGS] could not open relation

Felipe Amezquita wrote: Hola Felipe, por favor usa la lista pgsql-es-ayuda cuando quieras preguntar en español. Si quieres escribir a -bugs, hazlo en ingles. Gracias. > Les escribo en esta oportunidad para contarles algo que he analizado desde > el log,y que creo que pueda ser el inconveniento p

Re: [BUGS] BUG #3717: libpq needs .so version raised to 6

"Radim Kolar" <[EMAIL PROTECTED]> writes: > both libpq from pgsql 8.2 and 8.3 are using same version > of .so 5. But libpq from 8.3 have new function PQconnectionUsedPassword. .so > version of 8.3 libpq needs to be raised to 6 This is not a bug. Major version bumps in sonames are for incompatible

[BUGS] BUG #3717: libpq needs .so version raised to 6

The following bug has been logged online: Bug reference: 3717 Logged by: Radim Kolar Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3beta2 Operating system: FreeBSD Description:libpq needs .so version raised to 6 Details: /libexec/ld-elf.so.1: /usr/local/pgs

Re: [BUGS] BUG #3715: StackBuilder failing

Already fixed - theres an updated build at http://developer.pgadmin.org/~dpage/postgresql-8.3-beta2-2.zip Thanks for the report though. thanks, works fine now. maybe worth a short note in the download directory, so that others won't report the same thing? - thomas -

Re: [BUGS] BUG #3715: StackBuilder failing

> --- Original Message --- > From: "Thomas H." <[EMAIL PROTECTED]> > To: pgsql-bugs@postgresql.org > Sent: 02/11/07, 19:52:43 > Subject: Re: [BUGS] BUG #3715: StackBuilder failing > > > Bug reference: 3715 > > PostgreSQL version: 8.3b2 > > Operating system: Windows 2003 > > De

[BUGS] BUG #3716: utf8 crash with replace

The following bug has been logged online: Bug reference: 3716 Logged by: Andreas Pflug Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: Linux,Windows Description:utf8 crash with replace Details: If replace is used with UTF8 client_encodin

Re: [BUGS] I have a question about using index in order statement.

Tom Lane wrote: The basic reason that there's a problem here is that the parser is playing fast and loose by generating ORDER BY information that cites "text < text" as the sort operator but applies it to a bare varchar Var node. So I thought about a Plan B of changing the parser to put a correc

Re: [BUGS] BUG #3706: ecpg regression: "MOVE FORWARD"

I haven't seen any feedback on this report, but FYI... I worked around this problem by rewriting my code to use a dynamic prepared statement instead, e.g. OLD: EXEC SQL MOVE FORWARD :RowMove IN Sniffer; NEW: const char mover[] = "MOVE FORWARD ? IN Sniffer"; [...] EXEC SQL PREPARE MoverSQL FROM

Re: [BUGS] BUG #3715: StackBuilder failing

> Bug reference: 3715 > PostgreSQL version: 8.3b2 > Operating system: Windows 2003 > Description:StackBuilder failing some additional info to the just submitted bugreport: - pgAdminIII fails as well - postgres service starts fine - eventlog shows missing dependencies: Source: Sid

[BUGS] BUG #3715: StackBuilder failing

The following bug has been logged online: Bug reference: 3715 Logged by: Thomas Haegi Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3b2 Operating system: Windows 2003 Description:StackBuilder failing Details: This is on a vanilla 8.3b2 installation: running

Re: [BUGS] BUG #3714: applications using COPY are now much slower

"Radim Kolar" <[EMAIL PROTECTED]> writes: > Applications using COPY for batch insert few records are now much slower on > heavily updated table than in 8.2. Please give a *specific* test case showing what you are talking about... > I recommend to add some configuration file switch for switching

Re: [BUGS] BUG #3713: problem with thread safety???

Theodore Petrosky <[EMAIL PROTECTED]> writes: > as I don't know enough to tell what is happening, I > will attach the config.log... Well, you didn't need to look all that hard ... configure:24893: checking thread safety of required library functions configure:24921: gcc -no-cpp-precomp -o conftes

Re: [BUGS] tsvector that can't be dumped/reloaded in 8.3beta

Jeff Davis <[EMAIL PROTECTED]> writes: > I was unable to dump from beta1 to beta2, and I narrowed it down to this > simpler case: > test=> select tsvectorin(tsvectorout( > to_tsvector($foo$ a.b.cd/x=mnop.q\ $foo$) > )); > ERROR: syntax error in tsvector: "'a.b.cd':2 'a.b.cd/x':1 '/x=

[BUGS] BUG #3714: applications using COPY are now much slower

The following bug has been logged online: Bug reference: 3714 Logged by: Radim Kolar Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3 beta2 Operating system: BSD/64bit Description:applications using COPY are now much slower Details: Applications using COPY f

Re: [BUGS] I have a question about using index in order statement.

Heikki Linnakangas <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> I guess the right answer is to fix equivclass.c to strip RelabelTypes, >> and hope to maybe take that out again someday when all this gets cleaned >> up. > That certainly looks like the easier solution. We still strip > RelabelTy

[BUGS] tsvector that can't be dumped/reloaded in 8.3beta

I was unable to dump from beta1 to beta2, and I narrowed it down to this simpler case: test=> select tsvectorin(tsvectorout( to_tsvector($foo$ a.b.cd/x=mnop.q\ $foo$) )); ERROR: syntax error in tsvector: "'a.b.cd':2 'a.b.cd/x':1 '/x=mnop.q \':3" This has the same result on beta1

[BUGS] could not open relation

Que tal... Les escribo en esta oportunidad para contarles algo que he analizado desde el log,y que creo que pueda ser el inconveniento para que mi BD se ponga lenta. resulta que yo tengo instalado el Postgres 8.2 en windows 2003 server en la siguiente ruta estan los datos C:\Program Files\Postgre

Re: [BUGS] BUG #3713: problem with thread safety???

"Ted Petrosky" <[EMAIL PROTECTED]> writes: > checking thread safety of required library functions... no > configure: error: thread test program failed > This platform is not thread-safe. Check the file 'config.log'for the > exact reason. And? regards, tom lane -

[BUGS] BUG #3713: problem with thread safety???

The following bug has been logged online: Bug reference: 3713 Logged by: Ted Petrosky Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3 beta 2 Operating system: OS X 10.5 Description:problem with thread safety??? Details: whilst configuring on a new Leopard

Re: [BUGS] I have a question about using index in order statement.

Heikki Linnakangas <[EMAIL PROTECTED]> writes: > Attached is a patch that fixes that test case. I'm not very familiar > with that piece of code, though, and I have a sneaking suspicion that > the patch is either not general enough, there may be other places where > we should ignore relabel nodes

Re: [BUGS] I have a question about using index in order statement.

kevin wrote: Question: I have a question about using index in order statement. Why index ix_2 work by Seq Scan and index ix_3 work by Index Scan. Example : ix_2 condition : When I try explain select * from a_test order by code_ desc Postgresql response Sort (cost=11815.08..10

Re: [BUGS] Postgresql Domain Names

Andy.Xue wrote: > Dear Manager, > > We are China Net Technology Limited, which is the domain name register > center in China.I have something need to confirm with you. > we have received an application formally,one company named "LEALUI　 > Holdings Limited" applies for the domain > names(postg

[BUGS] Postgresql Domain Names

Dear Manager, We are China Net Technology Limited, which is the domain name register center in China.I have something need to confirm with you. we have received an application formally,one company named "LEALUI　Holdings Limited" applies for the domain names(postgresql.hk/postgresql.tw/postg

[BUGS] I have a question about using index in order statement.

Question: I have a question about using index in order statement. Why index ix_2 work by Seq Scan and index ix_3 work by Index Scan. Example : ix_2 condition : When I try explain select * from a_test order by code_ desc Postgresql response Sort (cost=11815.08..11852.56 rows=