Re: [BUGS] error

On 10/10/2013 7:18 AM, Andrius Di wrote: Hello, how to solve this error (please see attachment)? what exactly were you doing when you got this error, what Windows version was this on, etc etc? the error is pretty explicit, I would inspect the value of your COMSPEC environment variable. fo

Re: [BUGS] Error by restore a database

On Mon, Sep 9, 2013 at 11:38 PM, Sbis-Partner wrote: > Hello! > > When you restore a database error occurs > > «Pg_restore: creating TABLE dbschema > > pg_restore: [archiver (db)] Error from TOC entry 1428; 1259 83487 TABLE > dbschema User > > pg_restore: [archiver (db)] could not execute query: E

Re: [BUGS] Error by restore a database

On 9/9/2013 11:38 PM, Sbis-Partner wrote: When you restore a database error occurs «Pg_restore: creating TABLE dbschema pg_restore: [archiver (db)] Error from TOC entry 1428; 1259 83487 TABLE dbschema User pg_restore: [archiver (db)] could not execute query: ERROR: role "User" does not exi

Re: [BUGS] Error

Are you using persistent connections from your application? This would hold the connection to the database. So I think you have 2 choices: 1. Disable persistent connections 2. Increaes MAX_CONNECTIONS in postgresql.conf From: Bakyaraj K mailto:bakya...@railsfactory.org>> Date: Friday, May 24

Re: [BUGS] ERROR: syntax error in tsquery - for high-unicode whitespace

On Thu, Mar 14, 2013 at 11:56:19PM -0400, Tom Lane wrote: > hubert depesz lubaczewski writes: > > $ select to_tsquery('english', E'a\xe2\x80\x86a'); > > ERROR: syntax error in tsquery: "a a" > > > the 3-byte utf8 character is SIX-PER-EM SPACE (based on info from > > http://www.fileformat.info/in

Re: [BUGS] ERROR: syntax error in tsquery - for high-unicode whitespace

hubert depesz lubaczewski writes: > $ select to_tsquery('english', E'a\xe2\x80\x86a'); > ERROR: syntax error in tsquery: "a a" > the 3-byte utf8 character is SIX-PER-EM SPACE (based on info from > http://www.fileformat.info/info/unicode/char/2006/index.htm) AFAICS, that behavior is correct, i

Re: [BUGS] error

On Mon, Dec 10, 2012 at 11:24 AM, Abhishek Ramkumar wrote: > hello > every time i try to restore a file to the database i get the following > error > > > C:/Program Files/PostgreSQL/8.4/bin\pg_restore.exe --host localhost --port > 5432 --username postgres --dbname anchor --verbose "C:\Documents a

Re: [BUGS] ERROR - CREATE GIST INDEX on 9.2 beta3

On 15.08.2012 09:50, Heikki Linnakangas wrote: On 15.08.2012 01:02, Zdeněk Jílovec wrote: Hello, I use PostgreSQL 9.2beta3 with PostGIS 2.0.1 and if I try create GIST index on column geometry(Point,2065) I get error: test=> CREATE INDEX places_point ON places USING GIST(def_point); ERROR: fail

Re: [BUGS] ERROR - CREATE GIST INDEX on 9.2 beta3

On 15.08.2012 01:02, Zdeněk Jílovec wrote: Hello, I use PostgreSQL 9.2beta3 with PostGIS 2.0.1 and if I try create GIST index on column geometry(Point,2065) I get error: test=> CREATE INDEX places_point ON places USING GIST(def_point); ERROR: failed to re-find parent for block 18097 It works

Re: [BUGS] ERROR - Upgrading Postgresql 8.4.3 to Postgressql 9.1.4

On Tue, Aug 14, 2012 at 04:27:45PM -0400, Freddie Burgess wrote: > We are trying to upgrade our production postgres database instance that is > approximately 4TB in size and it contains various table partition structures.; > a separate tablespace for each partition. We were initially successful i

Re: [BUGS] Error on pg_settings.bytea_output for pg9.1

On Tue, Jul 31, 2012 at 9:07 AM, Guillaume Lelarge wrote: > On Tue, 2012-07-31 at 14:06 +0800, Craig Ringer wrote: >> On 07/31/2012 01:50 PM, Guillaume Lelarge wrote: >> >> Check the PgAdmin-III preferences; there may be an option to control its >> >> preferred bytea format. >> >> >> > There's no

Re: [BUGS] Error on pg_settings.bytea_output for pg9.1

On Tue, 2012-07-31 at 14:06 +0800, Craig Ringer wrote: > On 07/31/2012 01:50 PM, Guillaume Lelarge wrote: > >> Check the PgAdmin-III preferences; there may be an option to control its > >> preferred bytea format. > >> > > There's no option to control this. > > > Thanks for confirming that. > > Is

Re: [BUGS] Error on pg_settings.bytea_output for pg9.1

On 07/31/2012 01:50 PM, Guillaume Lelarge wrote: Check the PgAdmin-III preferences; there may be an option to control its preferred bytea format. There's no option to control this. Thanks for confirming that. Is it really best for PgAdmin-III to have a different default than Pg its self?

Re: [BUGS] Error on pg_settings.bytea_output for pg9.1

On Tue, 2012-07-31 at 10:19 +0800, Craig Ringer wrote: > On 07/30/2012 11:49 AM, Emcisc (JinWei) Zhao wrote: > > 5.Run the SQL query: "SELECT setting FROM pg_settings WHERE name = > > 'bytea_output'; " in pgAdmin3. It will show you the value 'escape'. > > > > 6.Run the client application 'psql' t

Re: [BUGS] Error on pg_settings.bytea_output for pg9.1

On 07/30/2012 11:49 AM, Emcisc (JinWei) Zhao wrote: 5.Run the SQL query: "SELECT setting FROM pg_settings WHERE name = 'bytea_output'; " in pgAdmin3. It will show you the value 'escape'. 6.Run the client application 'psql' to connect to the same DB server and database with the same user accou

Re: [BUGS] error connecting to postgresql by pgadmin

On Fri, Jun 8, 2012 at 5:06 AM, Renji Babu wrote: > I have installed PostgreSQL 9.1 on windows 7 and I am unable to connect > to the database after I restart the machine. > > When I first installed postgres from pgadmin III, Service started and > database also got connected. > > But when I shutdow

Re: [BUGS] Error with refering to the header files

"Ibrahim, Karim Aly Mohi Eldin" writes: > I’m new to postgres and I have some C files that execute sql commands in the > early parser stage.. > It has to include #include "libpq-fe.h" which is in the "interface" folder > not the "include" folder so I edited the make file like following: Not su

Re: [BUGS] ERROR: operator does not exist: integer = integer[]

On Thu, Apr 12, 2012 at 2:47 AM, cesar_cast wrote: > I have the following > > select * > from employee AS e > where (e.id) IN (ARRAY[3,1]); > Use: SELECT * FROM employee AS e WHERE e.id = ANY(ARRAY[3,1]); -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company

Re: [BUGS] ERROR: comparetup_datum() should not be called

y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes: > commit 337b6f5ecf05b21b5e997986884d097d60e4e3d0 marked comparetup_datum > "should not be called" but actually it is called for eg. tape-based sort. Yeah, that's pretty broken. Patch applied, thanks! regards, tom lane --

Re: [BUGS] Error calling function which returns a ROWTYPE from within another function

On 15.08.2011 08:54, Craig Miles wrote: I am experiencing unexpected behaviour on Postgres 9.0.4 using pl/pgsql relating to selecting from a function that returns a ROWTYPE into a ROWTYPE variable from within another function. In the example below I : 1) Create a table, TESTTABLE and insert a ro

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

> We have a customer in Japan who would be interested in this fix, in the > future. Would you like me to enter it as an official Postgres bug? > Sincerely, As I stated before, I don't regard this as a bug. BTW I wonder why you don't use CREATE CONVERSION which can be used for customer's problem

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

On Fri, Mar 25, 2011 at 03:33, Kasia Tuszynska wrote: > We have a customer in Japan who would be interested in this fix, in the > future. Would you like me to enter it as an official Postgres bug? Not a bug at all -- there are at least 3 versions of "EUCJP" encodings, and postgres just supports

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

...@gmail.come Cc: Kasia Tuszynska; pgsql-bugs@postgresql.org Subject: Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP > Agreed if the encoding is added as an user-defined encoding. > I don't want to add built-in encodings only for Japanese

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

> Agreed if the encoding is added as an user-defined encoding. > I don't want to add built-in encodings only for Japanese language any more. I do not agree here. Adding one more encoding/conversion is not big deal. Anyway these soltions would come to be real after one or two releases at the earli

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

On Wed, Mar 23, 2011 at 13:02, Tatsuo Ishii wrote: > I think what we can do best here is, adding new encoding and default > conversion. Agreed if the encoding is added as an user-defined encoding. I don't want to add built-in encodings only for Japanese language any more. -- Itagaki Takahiro -

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

>> So if we want to do a round trip conversion between >> EUC-JP and UTF-8, we have to choose either U+FF5E OR U+301C. We have >> chosen U+FF5E. If we change the mapping, many existing applications >> would break. > > I heard a request a few times for an additional one-directional conversion > fro

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

On Wed, Mar 23, 2011 at 10:58, Tatsuo Ishii wrote: > So if we want to do a round trip conversion between > EUC-JP and UTF-8, we have to choose either U+FF5E OR U+301C. We have > chosen U+FF5E. If we change the mapping, many existing applications > would break. I heard a request a few times for an

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

On Wed, Mar 23, 2011 at 08:05, Kasia Tuszynska wrote: > I was wondering if this was considered a bug, and if so what were the plans > to fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php The wave dash issue is not postgres-specific; some other converter just replace it with '

Re: [BUGS] ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP

> Hi, > I was wondering if this was considered a bug, and if so what were the plans > to fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php > > I searched the: pgsql-bug archive and found nothing > I also searched the wiki to do list and found nothing > But I could have missed

Re: [BUGS] Error mesage during installation

2011/3/5 Domčeky-Záhradné : > Good morning, > I was to install latest installation of your application: >  postgresql-9.0.3-1-windows.exe to my PC , > but there occored Error that you can see in attachment. I have Windows 7 - > 32 bit  system > Thank you for answer. That error comes from the Micro

Re: [BUGS] Error in sorting strings

Edoardo Serra wrote: > SELECT * FROM dummy ORDER BY string ASC; > string > > 100% > 10.1 > (2 rows) > > I would expect the order of the results to be '100%', '10.1'. > Moreover, if I use the following dataset, I get the correct sorting > > SELECT string, ascii(substr(string, 3, 1))

Re: [BUGS] Error to install postgre 9.0 beta 3

On Fri, Jul 30, 2010 at 5:48 AM, Thinh Nguyen wrote: > Hi support, > I had an error once I install postgre 9.0 beta 3 Windows 7 Professional > 64bits. The error message is "An error occured executing the Microsoft VC++ > runtime installer " > I need for help to install smoothly it. Can you send t

Re: [BUGS] ERROR: cannot handle unplanned sub-select

Merlin Moncure writes: > Not 100% sure I have a bug, but I've never seen this before so I > though it was worth a post. Confirmed on 8.4.4 and 9.0 beta. So let's see the test case ... regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To

Re: [BUGS] ERROR: failed to build any 3-way joins

Joshua Tolley writes: > On Sun, May 23, 2010 at 2:11 PM, Jehan-Guillaume (ioguix) de Rorthais > wrote: >> Here is how to reproduce the bug: >> postgres=# SELECT rolname FROM pg_catalog.pg_roles AS r, pg_auth_members AS m >> WHERE r.oid=m.roleid >> AND member IN ( >> SELECT oid FROM pg_catalog.pg_

Re: [BUGS] ERROR: failed to build any 3-way joins

On Sun, May 23, 2010 at 2:11 PM, Jehan-Guillaume (ioguix) de Rorthais wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > A user reported us the following bug under phpPgAdmin with 9.0beta1, but it > seems it comes from backend. > > Here is how to reproduce the bug: > > ==

Re: [BUGS] Error in ODBC

On Wed, May 12, 2010 at 10:52 AM, Osvaldor Ramirez wrote: > I dont know if it count but > > I had installed in my pc the ODBC Drivers of Postgresql version 8.03.01 but I > saw an new version ( 8.03.02 ) but with this driver show my this error: > > Windows Vista 06.00 Build 06000, SQLXpp: 3.1.24,

Re: [BUGS] Error while altering an inheritance hierarchy in mid-query

So I did miss something! Thanks for the brilliant explanation and simple solution, Tom. Bob --- On Thu, 3/18/10, Tom Lane wrote: > From: Tom Lane > Subject: Re: [BUGS] Error while altering an inheritance hierarchy in mid-query > To: "Bob Lunney" > Cc: pgsql-bugs

Re: [BUGS] Error while altering an inheritance hierarchy in mid-query

Bob Lunney writes: > 1. A select into query is run which summarizes the data from a partition > into a table outside the inheritance hierarchy, which is then indexed. > 2. Then > a. a transaction is begun, > b. the original partition is dropped, > c. the new table renamed to the orig

Re: [BUGS] Error when lock conflict on REPLACE function

On Tue, Mar 16, 2010 at 7:02 AM, Peter Eisentraut wrote: > On mån, 2010-03-15 at 14:13 -0700, Josh Berkus wrote: >> 1. Create a function. >> 2. In one session, start an explicit transaction. >> 3. Do a CREATE OR REPLACE on the same function, but do not commit. >> 4. Open a 2nd session, and an expl

Re: [BUGS] Error when lock conflict on REPLACE function

On mån, 2010-03-15 at 14:13 -0700, Josh Berkus wrote: > 1. Create a function. > 2. In one session, start an explicit transaction. > 3. Do a CREATE OR REPLACE on the same function, but do not commit. > 4. Open a 2nd session, and an explicit transaction in that session. > 5. Do a CREATE OR REPLACE on

Re: [BUGS] error after dropping column

Craig Ringer writes: > On 11/01/2010 10:27 PM, Filip Rembiałkowski wrote: >> ERROR: table row type and query-specified row type do not match >> DETAIL: Physical storage mismatch on dropped attribute at ordinal >> position 2. > I'm pretty certain that's not a bug. No, it is a bug, or at least

Re: [BUGS] error after dropping column

On 11/01/2010 10:27 PM, Filip Rembiałkowski wrote: Hi all, not sure if I should send it here; if it was reported before in pgsql-general. you can just ignore it :-) with postgres 8.2.4: create table test (t1 text); create function row2text(test) returns text as 'select $1::text' language sql i

Re: [BUGS] Error in exclusion constraint error message (8.5)?

Greg Stark writes: > But that still seems a bit more complex than ideal. Would it be > reasonable to have a tinterval() constructor which takes timestamptz > data types? No, because that would be encouraging people to use tinterval ;-). That type needs to die. If Jeff doesn't finish his range-ty

Re: [BUGS] Error in exclusion constraint error message (8.5)?

On Sat, Jan 2, 2010 at 1:37 PM, hubert depesz lubaczewski wrote: >    CONSTRAINT overlapping_times EXCLUDE USING GIST ( >        box( >            point( extract(epoch FROM from_ts at time zone 'UTC'), > extract(epoch FROM from_ts at time zone 'UTC') ), >            point( extract(epoch FROM to_t

Re: [BUGS] Error in exclusion constraint error message (8.5)?

hubert depesz lubaczewski writes: > 3rd insert fails (correctly), but I have doubts about its error message, > which was: > psql:z.sql:18: ERROR: conflicting key value violates exclusion constraint > "overlapping_times" > DETAIL: Key (box(point(date_part('epoch'::text, timezone('UTC'::text,

Re: [BUGS] ERROR: invalid page header in block 502758 of relation base/16388/16403

there is a database running on xen dom U, but the node (dom0) went down, we have a cluster, so the other node started the service and there is nothing that shows any problem unless i use SELECT on this database/table (this db contains only one table) there is no backup of the database. i can't see

Re: [BUGS] ERROR: invalid page header in block 502758 of relation base/16388/16403

fous velkej writes: > ok, so i did reindexing ending with following error > proxylog=# REINDEX TABLE user_record ; > ERROR: concurrent insert in progress So that page header wasn't the only corrupted data in your database. Maybe you'd better take a step back and tell us some context about your p

Re: [BUGS] ERROR: invalid page header in block 502758 of relation base/16388/16403

ok, fault on my side this is maybe better code dd if=16403.3.orig of=16403.3 bs=8192 count=109542 dd if=/dev/zero bs=8192 count=1 >> 16403.3 dd if=16403.3.orig skip=109543 bs=8192 >> 16403.3 but now, it says ERROR: index "day" contains unexpected zero page at block 502758 HINT: Please REINDEX i

Re: [BUGS] ERROR: invalid page header in block 502758 of relation base/16388/16403

fous velkej writes: > hi again > i've stopped postgres and done this > dd if=16403.3.orig of=16403.3 bs=8192 count=109541 > dd if=/dev/zero bs=8192 count=1 >> 16403.3 > dd if=16403.3.orig skip=109542 bs=8192 >> 16403.3 > then started postgres, but did not help, the same error appears. > ERROR: i

Re: [BUGS] ERROR: invalid page header in block 502758 of relation base/16388/16403

hi again i've stopped postgres and done this dd if=16403.3.orig of=16403.3 bs=8192 count=109541 dd if=/dev/zero bs=8192 count=1 >> 16403.3 dd if=16403.3.orig skip=109542 bs=8192 >> 16403.3 then started postgres, but did not help, the same error appears. ERROR: invalid page header in block 502758

Re: [BUGS] error: message type 0x5a arrived from server while idle

Robert Haas writes: > On Tue, Sep 8, 2009 at 11:38 PM, vyou zhi wrote: >> i use Python and PyGreSQL to link  PostgreSQL >> but the Python give me the error >> message type 0x43 arrived from server while idle >> message type 0x5a arrived from server while idle > This sounds like a bug in PyGreSQL

Re: [BUGS] error: message type 0x5a arrived from server while idle

On Tue, Sep 8, 2009 at 11:38 PM, vyou zhi wrote: > hi all: > > i use Python and PyGreSQL to link  PostgreSQL > but the Python give me the error > > the error here : > > ... > 95 > 93 > 95 > 97 > 94 > 96 > 94 > message type 0x43 arrived from server while

Re: [BUGS] ERROR: invalid page header in block 502758 of relation base/16388/16403

fous velkej writes: > i got following error while selecting from my db > ERROR: invalid page header in block 502758 of relation base/16388/16403 > i've found some solution in this thread > http://www.mail-archive.com/pgsql-gene...@postgresql.org/msg101644.html > but my problem is, that there a

Re: [BUGS] ERROR: XLogFlush: request AF/5703EDC8 is not satisfied --- flushed only to AF/50F15ABC

utsav wrote: Dear All, I am using postgres 7.3 version on RHEL 4.0. 7.3 is not a supported release any more you really need to look into getting something non-prehistoric - and what version of 7.3 exactly? My database has been restored. "restored" - how exactly? From a file system backup

Re: [BUGS] Error in PLpgSQL with SELECT INTO and composite types

Heikki Linnakangas writes: >SELECT '("(1)")'::btype INTO bvar; -- Should work, but errors No, because it's expecting the SELECT to yield a separate column for each column of the composite variable bvar. Something like SELECT ('("(1)")'::btype).* INTO bvar; would be correct. To make it wo

Re: [BUGS] ERROR: cache lookup failed for function 0

On Oct 25, 2008, at 05:35, Tom Lane wrote: Seems to be fixed in HEAD: regression=# SELECT '{foo}'::name[] <> '{bar}'::name[]; ERROR: operator is only a shell: name[] <> name[] LINE 1: SELECT '{foo}'::name[] <> '{bar}'::name[]; Great. Is it something that could be backported, or is it not wor

Re: [BUGS] ERROR: cache lookup failed for function 0

"David E. Wheeler" <[EMAIL PROTECTED]> writes: > Great. Is it something that could be backported, or is it not worth it? Not worth it IMO. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.p

Re: [BUGS] ERROR: cache lookup failed for function 0

"David E. Wheeler" <[EMAIL PROTECTED]> writes: > I ran into this error on 8.2 a while ago, and just figured out what > was causing it. Here's a quick example on 8.2: Seems to be fixed in HEAD: regression=# SELECT '{foo}'::name[] <> '{bar}'::name[]; ERROR: operator is only a shell: name[] <> na

Re: [BUGS] ERROR: unexpected data beyond EOF in block XXXXX of relation "file"

David Fetter wrote: On Sun, Sep 28, 2008 at 11:51:49AM -0700, austijc wrote: That's going to be a problem for the continued viability of Postgres. Funny, I thought running a DBMS over a known-unreliable storage system was a problem for the continued viability of Oracle. When, not if, people l

Re: [BUGS] ERROR: unexpected data beyond EOF in block XXXXX of relation "file"

Okay, I see the maturity level is too low here. I'll take this elsewhere. If anyone has a similar problem and would like to know the status please email me. David Fetter wrote: > > On Sun, Sep 28, 2008 at 11:51:49AM -0700, austijc wrote: >> >> That's going to be a problem for the continued

Re: [BUGS] ERROR: unexpected data beyond EOF in block XXXXX of relation "file"

On Sun, Sep 28, 2008 at 11:51:49AM -0700, austijc wrote: > > That's going to be a problem for the continued viability of > Postgres. Funny, I thought running a DBMS over a known-unreliable storage system was a problem for the continued viability of Oracle. When, not if, people lose enough data t

Re: [BUGS] ERROR: unexpected data beyond EOF in block XXXXX of relation "file"

That's going to be a problem for the continued viability of Postgres. Clustered systems using a NAS for data is a pretty common configuration these days. Oracle specifically supports it and even complains if your NFS mount options are not correct. Our Oracle DBs run great in this same configur

Re: [BUGS] ERROR: unexpected data beyond EOF in block XXXXX of relation "file"

austijc <[EMAIL PROTECTED]> writes: > The question is can anyone more familiar with this tell me what's going on > here? I don't know if this is a Postgres, Sun, or NetApp issue. Could it > be a work around for an old Linux bug causing an issue with acceptable > behavior of the NetApp device? P

Re: [BUGS] Error in starting PostgreSQL Server 7.4 after crash

sagar koirala <[EMAIL PROTECTED]> writes: > So, I used pg_resetxlog PGDATA with PGDATA pointing to my current > /pgsql/data. It said transaction log reset. At this point, the postgresql is > not running, so I cannot dump my old data. Starting the postgresql doesn't > work. > So I tried: export

Re: [BUGS] Error while loading shared libraries

[EMAIL PROTECTED] wrote: > Hello, > I have installed postgresql, version 8.3.3. Some information you left out would be useful, such as: - Operating system - Version of operating system - How you obtained and installed PostgreSQL (from where, how you built it if you built it yourself, etc) - ... a

Re: [BUGS] error ' Client encoding Mismatch' with Version 8.1.4

l Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2008 8:29 PM To: Ashutosh Kumar S-TLS,Chennai Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] error ' Client encoding Mismatch' with Version 8.1.4 "Ashutosh Kumar S-TLS,Chennai" <[EMAIL PR

Re: [BUGS] error ' Client encoding Mismatch' with Version 8.1.4

"Ashutosh Kumar S-TLS,Chennai" <[EMAIL PROTECTED]> writes: > Problem is whenever I am trying to open the database through ODBC > connection it throws an error 'Client encoding mismatch'. That phrase occurs noplace in Postgres 8.1, so the error must be coming from something on the client side. We

Re: [BUGS] error message "psql: expected authentication request from server, but received " when using psql to connect remote database

"TIAN Justin" <[EMAIL PROTECTED]> writes: > Actually, we don't directly use postgre server,we open TCP connection to > support postgre wire protocol, so psql client can connect to our > application, > I found the problem is in the StartupMessage, when psql client version > is 8.1.4, the major and m

Re: [BUGS] error message "psql: expected authentication request from server, but received " when using psql to connect remote database

9:43 PM To: TIAN Justin Cc: Heikki Linnakangas; pgsql-bugs@postgresql.org Subject: Re: [BUGS] error message "psql: expected authentication request from server, but received " when using psql to connect remote database "TIAN Justin" <[EMAIL PROTECTED]> writes: > Thanks f

Re: [BUGS] error message "psql: expected authentication request from server, but received " when using psql to connect remote database

"TIAN Justin" <[EMAIL PROTECTED]> writes: > Thanks for your quick response; the server we used is 8.1.4, > The error when using client 8.1.4, >> psql -U or -p -d testdb -h localhost > Output: > psql: expected authentication request from server, but received What is in the server's pg_hba.con

Re: [BUGS] error message "psql: expected authentication request from server, but received " when using psql to connect remote database

tdb -h localhost Output: Password: Then enter password, it can log in and do all operation. Thanks, Justin -Original Message- From: Heikki Linnakangas [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21, 2008 8:14 PM To: TIAN Justin Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] error m

Re: [BUGS] error message "psql: expected authentication request from server, but received " when using psql to connect remote database

TIAN Justin wrote: I met an error, when psql client version is 8.1.4, I use it to connect to remote database or local database, such as "psql -U name -p -d -h ", it will prompt error message "psql: expected authentication request from server, but received ", but if the client version is 8.0.3,

Re: [BUGS] ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target

John Parnefjord > Cc: pgsql-bugs@postgresql.org; Tom Lane > Subject: Re: [BUGS] ERROR: failed to re-find parent key in > "sl_seqlog_idx" for deletion target > > John Parnefjord wrote: > > > Please copy out the files as requested in that email - I'm sure Tom >

Re: [BUGS] ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target

John Parnefjord wrote: > > Please copy out the files as requested in that email - I'm sure Tom > > is still interested in debugging it to find the issue. After that, > > try a REINDEX to see if it solves your problem. > > Ok, see the snippets below. I just cut them from the PgAdminIII > interface.

Re: [BUGS] ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target

> Please copy out the files as requested in that email - I'm sure Tom is > still interested in debugging it to find the issue. After that, try a > REINDEX to see if it solves your problem. Ok, see the snippets below. I just cut them from the PgAdminIII interface. Drop me a mail if you need more i

Re: [BUGS] ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target

John Parnefjord wrote: > Hi! > > Hope anyone can shed some light on this. I was struck by the > following error in the slony log but I believe it's not a slony > error, rather that slony triggers an error in PostgreSQL. The error > message is: Correct, that's not a backend error. > cleanupThrea

Re: [BUGS] error php - postgresql

On Fri, Apr 11, 2008 at 5:31 PM, jalvarez <[EMAIL PROTECTED]> wrote: > i have that error where execute page > > server closed the connection unexpectedly This probably means the server > terminated abnormally before or while processing the request postgres linux Please dig a bit further before co

Re: [BUGS] ERROR: RETURN NEXT must specify a record or row variable in function returning tuple

DECLARE v_row record; BEGIN select 1, row( 1,2) as result into v_row; return next v_row.result END; This code cause "ERROR: RETURN NEXT must specify a record or row variable in function returning tuple" BUG? TODO? DECLARE v_row record; DECLARE v_result record; BEGIN select 1, row( 1,2) as result

Re: [BUGS] Error during hash index scans can cause postgres halt!

"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Ouch. So this has been broken (by me, I think :-() since 8.0. Tells >> you something about how many people use hash indexes :-( > Yeah. Also, this is very hard to trigger without --enable-cassert (or > just CLOBBER_FREED_MEMO

Re: [BUGS] Error during hash index scans can cause postgres halt!

I wrote: > Ouch. So this has been broken (by me, I think :-() since 8.0. Tells > you something about how many people use hash indexes :-( Actually it's not that bad --- this particular test case doesn't crash in 8.0 or 8.1. I'm guessing we rearranged the order of transaction abort processing in

Re: [BUGS] Error during hash index scans can cause postgres halt!

Tom Lane wrote: "Heikki Linnakangas" <[EMAIL PROTECTED]> writes: I can reproduce this, with --enable-cassert. It crashes when aborting the transaction, in ReleaseResources_hash. The HashScanList items are allocated in ExecutorState memory context, but that context has already been deleted by t

Re: [BUGS] Error during hash index scans can cause postgres halt!

"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > I can reproduce this, with --enable-cassert. It crashes when aborting > the transaction, in ReleaseResources_hash. The HashScanList items are > allocated in ExecutorState memory context, but that context has already > been deleted by the time we

Re: [BUGS] Error during hash index scans can cause postgres halt!

ykhuang wrote: recurred through deadlock. client1: create table test(a int); create index id on test using hash(a); insert into test values(1); insert into test values(2); set enable_seqscan=off; begin; update test set a=a+1 where a=1; client2: set enable_seqscan=off; begin; update te

Re: [BUGS] Error happen when Compile C program

hello you need install libpq library - it's client library for postgresql Regards Pavel Stehule On 19/01/2008, 苏睿 <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] primary_db_la]# make clean;make > rm --force run_db > rm --force *.bak > rm --force *.orig > gcc -L /usr/lib -lpq -o run_db \ >

Re: [BUGS] error while starting database

All I can tell you, based on this information, Nitin, is that your postmaster is not started, and it is failing to start for some reason. Without any additional information, there is absolutely nothing I can tell you. Try listing the /var/lib/pgsql/data folder. Verify that it does exist

Re: [BUGS] error while starting database

"Nitin Saxena" <[EMAIL PROTECTED]> writes: > All the command such asgives following output; > 1: :ls -a/tmp: No such file or directory >2 : "rm -f/tmp/.s.PGSQL.5432" > bash: rm -f/tmp/.s.PGSQL.5432: No such file or directory The reason these commands aren't working for you is

Re: [BUGS] error while starting database

"Douglas Toltzman" <[EMAIL PROTECTED]> writes: > In any case, the server specifically calls out an error creating > "/tmp/.s.PGSQL.5432". I would start by creating a world-writable /tmp > folder. FWIW the correct permissions for /tmp on Unix machines is 1777. It should look like this (note the "t

Re: [BUGS] error while starting database

821 unix 2 [ ] DGRAM785 unix 2 [ ] STREAM CONNECTED 525 Please help as it is urgent. Regards: Nitin Saxena 91-985709 -- Forwarded message -- From: Nitin Saxena <[EMAIL PROTECTED]> Date: Aug 18, 2007 8:42 AM

Re: [BUGS] error while starting database

Hi All the command such asgives following output; 1: :ls -a/tmp: No such file or directory 2 : "rm -f/tmp/.s.PGSQL.5432" bash: rm -f/tmp/.s.PGSQL.5432: No such file or directory 3:"ps -ax|grep postgres" bash: ps -ax|grep postgres: command not found Does PID in postmast

Re: [BUGS] error while starting database

If it is true that listing /tmp (ls -a /tmp) returns no such file or directory, then that may be the problem. You should have a world- writable /tmp folder, as Tom already pointed out. Also, an update to a more stable version of PostgreSQL is still highly recommended. On Aug 17, 2007, at 1

Re: [BUGS] error while starting database

"Nitin Saxena" <[EMAIL PROTECTED]> writes: > I am using postgres 7.0 on linux platform. Egad. At first I thought that was a typo, but if psql really spelled its error message just like that, it must indeed be 7.0 or older :-(. Do yourself a favor and get onto a newer version, NOW. Not tomorrow.

Re: [BUGS] error while starting database

PostgreSQL version 7.0 is really, really out of date, but as far as I know, it should still work. I generally use "ps -ax | grep postges" to see if there is a postgres process running. Also, I use "netstat -a" to see open sockets and listening servers. Have you removed the socket file in

Re: [BUGS] Error message that is a bit misleading / weird result from || null

Frank van Vugt <[EMAIL PROTECTED]> writes: > While trying to find a way to get indexed access to a table based on it's > xmin, I ran into the following error message that seems a bit misleading: > db=# select xmin || ' ' from limit 1; > ERROR: array value must start with "{" or dimension inform

Re: [BUGS] Error message that is a bit misleading / weird result from || null

"Frank van Vugt" <[EMAIL PROTECTED]> writes: > Sidenote: since it does solve my problem, I can now build an index based on > such an interpretation of xmin, I'm a bit anxious as to how this will > be 'fixed', if at all ;) Actually this was noticed only recently but that was precisely because i

Re: [BUGS] ERROR: invalid input syntax for integer: ""

Magnus Hagander <[EMAIL PROTECTED]> writes: > IIRC, the behavior of MSSQL will depend on the query plan. If it's a > plan that requires doesn't require materialization at all, it won't > figure it out until you get there. ... which is pretty much what we do, too. regards,

Re: [BUGS] ERROR: invalid input syntax for integer: ""

Pit M. wrote: > >> It would have failed if you had run the cursor far enough to fetch one >> of the bad rows. >> >> regards, tom lane >> > The difference is that in one case the query fails and in the other the > FETCH command fails. > > > Our problem is that if a query succeeds we u

Re: [BUGS] ERROR: invalid input syntax for integer: ""

It would have failed if you had run the cursor far enough to fetch one of the bad rows. regards, tom lane The difference is that in one case the query fails and in the other the FETCH command fails. Our problem is that if a query succeeds we use a count(*) of that q

Re: [BUGS] ERROR: invalid input syntax for integer: ""

"Pit M." <[EMAIL PROTECTED]> writes: > Following query fails in pgAdmin which is OK because the field PLZZ > contains characters: > select * from "PERSONEN" where (CAST("PERSONEN"."PLZZ" AS INTEGER) >= > 7 ); > but if using the same query with a cursor ist works: > START TRANSACTION; > DE

Re: [BUGS] ERROR: tuple concurrently updated

: Zubkovsky, Sergey Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] ERROR: tuple concurrently updated "Zubkovsky, Sergey" <[EMAIL PROTECTED]> writes: > create table t1 ( id int ); > create temp view v1 as select * from t1; > C1: begin; drop view v1; > C2: drop table t1;

Re: [BUGS] ERROR: tuple concurrently updated

"Zubkovsky, Sergey" <[EMAIL PROTECTED]> writes: > create table t1 ( id int ); > create temp view v1 as select * from t1; > C1: begin; drop view v1; > C2: drop table t1; > C1: commit; This seems a variant of the problem noted by Michael Fuhr some time ago: http://archives.postgresql.org/pgsql-hacke

  1   2   3   >