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

[BUGS] error

Hello, how to solve this error (please see attachment)? Regards, AnDi <> -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] error during the installation with the installer postgresql-9.2.4-1-windows.exe

I got the following error message (pop-up) in the end of PostgreSQL9.2 installation on Windows 7 32-bit machine: "Problem running post-install step. Installation may not complete correctly. The database cluster initialization failed." I did the installation by using the downloaded installer postg

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

[BUGS] Error by restore a database

Hello! When you restore a database error occurs . Please help me to solve this problem.

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

y, May 24, 2013 4:40 AM To: "pgsql-bugs@postgresql.org<mailto:pgsql-bugs@postgresql.org>" mailto:pgsql-bugs@postgresql.org>> Subject: [BUGS] Error Hi, I am facing this issues when i use postgresql database. FATAL: remaining connection slots are reserved for non-replic

[BUGS] Error

Hi, I am facing this issues when i use postgresql database. * FATAL: remaining connection slots are reserved for non-replication superuser connections* Postgresql 9.2 version. Could you help me and how to resolve the issue. -- *Thanks.,* *Bakyaraj K* *Linux Server Administrator* *Sedin T

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

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

hi it was tested on 9.1 and 9.3. Interestingly - it worked without error in 8.2. $ 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)

[BUGS] ERROR: invalid input syntax for type timestamp with time zone

Hi All, Consider the following test: postgres=# select version(); version - PostgreSQL 9.3devel on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4), 6

[BUGS] error reading c:\Program Files\PostgreSQL\8.3\data\postgresql.conf during installation

Installer 9.0 for Vista32 error reading c:\Program Files\PostgreSQL\8.3\data\postgresql.conf during installation tried this solution: http://www.postgresql.org/message-id/49782810.9050...@cpttm.org.mo Message for access denied Ran on Command Prompts as admin. Pls help

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

[BUGS] ERROR - CREATE GIST INDEX on 9.2 beta3

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 on 9.1 I can send a table dump (43 MB - bzip

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

[BUGS] ERROR - Upgrading Postgresql 8.4.3 to Postgressql 9.1.4

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 in performing the upgrade using pg_upgrade with both the link and copy o

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

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

Hi pgsql developers: 1 . Postgres 9.1, database server OS platform: Linux x86_64 and Windows XP Professional Version 2002 SP3 Client OS platform: Linux x86_64 , Windows XP Professional Version 2002 SP3, Windows Server 2003 Standard Edition SP2 2. pgAdminIII: version 1.14.3, or the defaul

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

[BUGS] error in connecting to Postgresql 9.1

Hi, 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 shutdown and tried to start the service again, it is showing as th

[BUGS] error connecting to postgresql by pgadmin

Hi, 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 shutdown and tried to start the service again, it is showing as

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

[BUGS] Error with refering to the header files

Hi , 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: #--

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

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

I have the following select * from employee AS e where (e.id) IN (ARRAY[3,1]); I have the following mistake ERROR: operator does not exist: integer = integer[] LINE 3: where (e.id) IN (ARRAY[3,1]); ^ HINT: No operator matches the given name and argument type(s). You

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 --

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

hi, commit 337b6f5ecf05b21b5e997986884d097d60e4e3d0 marked comparetup_datum "should not be called" but actually it is called for eg. tape-based sort. a testcase: select generate_series(1,100) a into t; set maintenance_work_mem=1024; create index concurrently i on t (a)

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

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

Dear Postgres Support 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 row. 2) Create a func

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

[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 it. Sincerel

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

[BUGS] Error mesage during installation

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. DOMČEKY-ZÁHRADNÉ Ing. Jozef Hrčka Jánskeho 12, 949 01 NITRA tel:

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))

[BUGS] Error in sorting strings

Hi guys, I found a weird behaviour in sorting character varying columns, I think it could really be a bug. Table definition: CREATE TABLE dummy (string character varying(255)); Test dataset: INSERT INTO dummy VALUES ('10.'); INSERT INTO dummy VALUES ('100'); If I query the table sorting

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

[BUGS] Error to install postgre 9.0 beta 3

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. Thanks Thinh

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

[BUGS] ERROR: cannot handle unplanned sub-select

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. I have a small self contained test case that I can send off line or on the list following some code obfuscation (it's fairly complex to set up). merlin -- Sent via pgs

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: > > ==

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

-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: > postgres=# SELECT version(); version - -

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,

[BUGS] Error in ODBC

Hello guys 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, Runtime: 1.90.355 SQLState: 07009,  ErrorCode:13 Invalid

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

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

My database implements partitioning using inheritance and constraint exclusion, as described in the fine manual. Each partition holds data for a single day, and there are well over 300 child partitions. The exception mentioned below notwithstanding, the technique works exceedingly well and i

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

[BUGS] Error when lock conflict on REPLACE function

Severity: Annoyance Versions Tested: 8.4.2 Platform: Linux RHEL 5.4 Reproduceable: always Steps to reproduce: 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 transactio

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

[BUGS] error after dropping column

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 immutable; create index test_row2text_idx on test( row

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,

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

Hi, I tried to use exclusion for time ranges, with this table and data: CREATE TABLE test ( from_ts TIMESTAMPTZ, to_ts TIMESTAMPTZ, CHECK ( from_ts < to_ts ), CONSTRAINT overlapping_times EXCLUDE USING GIST ( box( point( extract(epoch FROM from_ts at time zone

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

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

hi, 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 are multiple files with sim

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

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 idle message type 0x5a arrived from server while idle INSERT INTO code (stock_

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

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

Dear All, I am using postgres 7.3 version on RHEL 4.0. My database has been restored. All tables all working fine i.e select , update but on a particular table its showing error "ERROR: XLogFlush: request AF/5703EDC8 is not satisfied --- flushed only to AF/50F15ABC " I have searched other

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

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

Tested on 8.2, 8.3 and CVS HEAD: CREATE TYPE atype AS (a int); CREATE TYPE btype AS (compcol atype); CREATE FUNCTION foofunc() RETURNS void AS $$ declare avar atype; bvar btype; begin SELECT '("(1)")'::btype INTO bvar; -- Should work, but errors end; $$ LANGUAGE plpgsql; SELECT foofunc(

[BUGS] error reading c:\Program Files\PostgreSQL\8.3\data\postgresql.conf during installation

Package: One click installer of PostgreSQL 8.3 Env: Windows XP SP2 (Traditional Chinese) What's wrong: It says error reading c:\Program Files\PostgreSQL\8.3\data\postgresql.conf during installation. That data directory is empty. Obviously, you can't start the server later. Fix: This error is

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

[BUGS] ERROR: cache lookup failed for function 0

Howdy, 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: BEGIN; -- Compare name[]s more or less like 8.3 does. CREATE OR REPLACE FUNCTION namearray_text(name[]) RETURNS TEXT AS 'SELECT textin(array_out($1));' LANGUAGE sql IMMUT

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

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

Configuration: Postgres 8.3.1 Solaris 10 Sparc System NFS mounting the database directory from a NetApp 2020 NAS device. Mount options: rw,bg,hard,rsize=32768,wsize=32768,vers=3,forcedirectio,nointr,proto=tcp,suid Error: ERROR: unexpected data beyond EOF in block 315378 of relation "file" HI

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

[BUGS] Error in starting PostgreSQL Server 7.4 after crash

It all started like this: My postgresql 7.4 running in CentOS crashed with one database missing in all my backups. But, I have a copy of the entire pgsql/data directory (which is unforunately a version grabbed while the server was still running...) I need to recover that database and I have tri

[BUGS] Error connecting

So it just suddenly stopped working after 1 week for the 2nd time straight. The first time i reinstalled everything, lost database but it worked, now it just doesnt connect. What should i do? I use windows vista, run as administrator and everything

  1   2   3   4   >