Re: [GENERAL] Fatal error "stack empty" on ROLLBACK

l - A New Database Language - andl.org > -Original Message- > From: Tom Lane [mailto:t...@sss.pgh.pa.us] > Sent: Tuesday, 24 May 2016 2:56 AM > To: dandl > Cc: 'PostgreSQL' > Subject: Re: [GENERAL] Fatal error "stack empty" on ROLLBACK > > &

Re: [GENERAL] Fatal error "stack empty" on ROLLBACK

"dandl" writes: > SPI call to execute "ROLLBACK" triggers FATAL ERROR "stack empty". What does > it mean? Nothing in the docs I can see. I can't find that string anywhere in the Postgres sources. However, SPI should refuse to execute ROLLBACK, or any other transaction control command; it should

[GENERAL] Fatal error "stack empty" on ROLLBACK

SPI call to execute "ROLLBACK" triggers FATAL ERROR "stack empty". What does it mean? Nothing in the docs I can see. In the particular case there were no update commands issued between BEGIN and ROLLBACK. Is that what it means? Or am I missing something? Regards David M Bennett FACS Andl - A New

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

On 02/04/2016 01:35 PM, drum.lu...@gmail.com wrote: On 4 February 2016 at 12:03, David G. Johnston mailto:david.g.johns...@gmail.com> >> wrote: On Wed, Feb 3, 2016 at 3:48 PM, drum

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

> > >> On 4 February 2016 at 12:03, David G. Johnston >> mailto:david.g.johns...@gmail.com>> wrote: >> >> On Wed, Feb 3, 2016 at 3:48 PM, drum.lu...@gmail.com >> > >wrote: >> >> Hi all, >> >> Below is an example

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

On 02/03/2016 03:09 PM, drum.lu...@gmail.com wrote: On 4 February 2016 at 12:03, David G. Johnston mailto:david.g.johns...@gmail.com>> wrote: On Wed, Feb 3, 2016 at 3:48 PM, drum.lu...@gmail.com mailto:drum.lu...@gmail.com>>wrote: Hi all,

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

On 2/3/2016 3:32 PM, Andreas Joseph Krogh wrote: This query works for me in 9.5: SELECT CAST(customer_id AS BIGINT), csv_data, freshbooks_id, myob_id, ppy_id, qb_id, xero_id, _iid FROM ( VALUES ('3915105', E'\x1A', E'\x1A', 'c59894cb-0ffe-4ad6-823d-73c1392142b6', E'\x1A', E'\x1A', E'\x1A', '44

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

On Wed, Feb 3, 2016 at 4:09 PM, drum.lu...@gmail.com wrote: > > > On 4 February 2016 at 12:03, David G. Johnston > wrote: > >> On Wed, Feb 3, 2016 at 3:48 PM, drum.lu...@gmail.com < >> drum.lu...@gmail.com> wrote: >> >>> Hi all, >>> >>> Below is an example of the auto-generated update query, wit

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

På torsdag 04. februar 2016 kl. 00:09:41, skrev drum.lu...@gmail.com < drum.lu...@gmail.com >:     On 4 February 2016 at 12:03, David G. Johnston mailto:david.g.johns...@gmail.com>> wrote: On Wed, Feb 3, 2016 at 3:48 PM, drum.lu...@gmail.com

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

On 4 February 2016 at 12:03, David G. Johnston wrote: > On Wed, Feb 3, 2016 at 3:48 PM, drum.lu...@gmail.com > wrote: > >> Hi all, >> >> Below is an example of the auto-generated update query, with >> client-supplied keys (_iid). There's a fatal error when _iid is not >> numeric. However; this s

Re: [GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

On Wed, Feb 3, 2016 at 3:48 PM, drum.lu...@gmail.com wrote: > Hi all, > > Below is an example of the auto-generated update query, with > client-supplied keys (_iid). There's a fatal error when _iid is not > numeric. However; this should accept any value. > > *Question:* How could I do something t

[GENERAL] Fatal error when not numeric value - PostgreSQL 9.2

Hi all, Below is an example of the auto-generated update query, with client-supplied keys (_iid). There's a fatal error when _iid is not numeric. However; this should accept any value. *Question:* How could I do something that would allow _iid to be more than just an INT? WITH in_rows AS (

Re: [GENERAL] FATAL error could not find function "alt_to_mic" in file cyrillic_and_mic.so

Please reply to the list, not just to me. My reply follows inline. Jayaraman, Rajaram (STSD) wrote: > I replaced the file conversion_create.sql and the db got created. Yes, but you never found out why it happened in the first place. I strongly suspect your install is busted, probably due to an i

Re: [GENERAL] FATAL error could not find function "alt_to_mic" in file cyrillic_and_mic.so

Jayaraman, Rajaram (STSD) wrote: > I have compiled PostgreSQL version 8.4.1 on HPUX 11iV3 (HPUX 11.31) on a > ia64 hp server BL870c. When I try to start the database it creates the > data directory and while initializing it gets till creating conversions > and then throws a FATAL error “could not

Re: [GENERAL] FATAL error "could not find function "alt_to_mic" in file cyrillic_and_mic.so

takes that separate true leaders from the rest of the pack. -Original Message- From: Jayaraman, Rajaram (STSD) Sent: Friday, October 23, 2009 4:10 PM To: 'Tom Lane' Cc: pgsql-general@postgresql.org Subject: RE: [GENERAL] FATAL error "could not find function &

Re: [GENERAL] FATAL error "could not find function "alt_to_mic" in file cyrillic_and_mic.so

neral@postgresql.org Subject: Re: [GENERAL] FATAL error "could not find function "alt_to_mic" in file cyrillic_and_mic.so "Jayaraman, Rajaram (STSD)" writes: > I have compiled PostgreSQL version 8.4.1 on HPUX 11iV3 (HPUX 11.31) on a ia64 > hp server BL870c.

Re: [GENERAL] FATAL error "could not find function "alt_to_mic" in file cyrillic_and_mic.so

"Jayaraman, Rajaram (STSD)" writes: > I have compiled PostgreSQL version 8.4.1 on HPUX 11iV3 (HPUX 11.31) on a ia64 > hp server BL870c. When I try to start the database it creates the data > directory and while initializing it gets till creating conversions and then > throws a FATAL error "coul

[GENERAL] FATAL error "could not find function "alt_to_mic" in file cyrillic_and_mic.so

Hi I have compiled PostgreSQL version 8.4.1 on HPUX 11iV3 (HPUX 11.31) on a ia64 hp server BL870c. When I try to start the database it creates the data directory and while initializing it gets till creating conversions and then throws a FATAL error "could not find function "alt_to_mic" in file

[GENERAL] FATAL error could not find function "alt_to_mic" in file cyrillic_and_mic.so

Hi I have compiled PostgreSQL version 8.4.1 on HPUX 11iV3 (HPUX 11.31) on a ia64 hp server BL870c. When I try to start the database it creates the data directory and while initializing it gets till creating conversions and then throws a FATAL error "could not find function "alt_to_mic" in file

Re: [GENERAL] Fatal error on start

Thanks, I found it, a permissions issue using sudo to start postgres. Thanks anyway. 2009/10/6 纪晓曦 > Did you delete some log or data in your PGDATA directory? > > 2009/10/6 Andrew Bartley > > does anyone know what this is? >> >> Trying to start postgres version: >> PostgreSQL 8.3.7 on i486-pc

[GENERAL] Fatal error on start

does anyone know what this is? Trying to start postgres version: PostgreSQL 8.3.7 on i486-pc-linux-gnu, compiled by GCC gcc-4.3.real (Debian 4.3.2-1.1) 4.3.2 2009-10-06 15:17:21 EST 3757 FATAL: XX000: could not open directory "pg_tblspc": Unknown error 530 2009-10-06 15:17:21 EST 3757 LOCATION

Re: [GENERAL] fatal error on 8.1 server

Tom Lane wrote: Alvaro Herrera <[EMAIL PROTECTED]> writes: Tony Caduto wrote: I did not have autovacuum turned on and I usually do a vacuumdb -z -a -f -q each night but this one slipped through the cracks :-( Strange -- autovacuum should have started an automatic database-

Re: [GENERAL] fatal error on 8.1 server

Alvaro Herrera <[EMAIL PROTECTED]> writes: > Tony Caduto wrote: >> I did not have autovacuum turned on and I usually do a vacuumdb -z -a -f >> -q each night but this one slipped through the cracks :-( > Strange -- autovacuum should have started an automatic database-wide > vacuum on that databas

Re: [GENERAL] fatal error on 8.1 server

Tony Caduto wrote: > Martijn van Oosterhout wrote: > >On Mon, Nov 27, 2006 at 02:22:19PM -0600, Tony Caduto wrote: > > > >>Just in case anyone is interested I did get it up and running with no > >>damage to the system. > >>It took well over a year for it to reach the 1 million threshold mark.

Re: [GENERAL] fatal error on 8.1 server

Martijn van Oosterhout wrote: On Mon, Nov 27, 2006 at 02:22:19PM -0600, Tony Caduto wrote: Just in case anyone is interested I did get it up and running with no damage to the system. It took well over a year for it to reach the 1 million threshold mark. You mean one *billion*, right?

Re: [GENERAL] fatal error on 8.1 server

On Mon, Nov 27, 2006 at 02:22:19PM -0600, Tony Caduto wrote: > Just in case anyone is interested I did get it up and running with no > damage to the system. > It took well over a year for it to reach the 1 million threshold mark. You mean one *billion*, right? That's one busy server! Hopeeful

Re: [GENERAL] fatal error on 8.1 server

Alvaro Herrera wrote: Stop the postmaster, start a standalone backend, and issue a database-wide VACUUM on database postgres. Just in case anyone is interested I did get it up and running with no damage to the system. It took well over a year for it to reach the 1 million threshold mark. T

Re: [GENERAL] fatal error on 8.1 server

On Mon, 2006-11-27 at 13:36 -0600, Tony Caduto wrote: > Alvaro Herrera wrote: > > Tony Caduto wrote: > > > >> I don't know what the exact version is but I am getting this: > >> > >> FATAL: database is not accepting commands to avoid wraparound data loss > >> in database "postgres" > >> > >> Ho

Re: [GENERAL] fatal error on 8.1 server

Alvaro Herrera wrote: Tony Caduto wrote: I don't know what the exact version is but I am getting this: FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres" How can I recover from this and why woud this happen to the postgres database? Has my se

Re: [GENERAL] fatal error on 8.1 server

Tony Caduto wrote: > I don't know what the exact version is but I am getting this: > > FATAL: database is not accepting commands to avoid wraparound data loss > in database "postgres" > > How can I recover from this and why woud this happen to the postgres > database? Has my server been hacke

[GENERAL] fatal error on 8.1 server

I don't know what the exact version is but I am getting this: FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres" How can I recover from this and why woud this happen to the postgres database? Has my server been hacked? there should be no inserts

Re: [GENERAL] Fatal error while installing

Go to Start/ Control Panel / Administrative tools / Computer Management / and you see Local Users and groups Delete the user from there - Original Message - From: "Gibson" <[EMAIL PROTECTED]> Cc: "pgsql general" Sent: Friday, September 01, 2006 2:31 AM Su

Re: [GENERAL] Fatal error while installing

How do i remove this user?I am running on Win XP here. Joshua D. Drake wrote: Gibson wrote: I seem to get this error "user postgres could not be created, user account already exists" when trying to install postgres. Anyone knows how to fix this? Sounds to me like the user postgres on the OS

Re: [GENERAL] Fatal error while installing

Gibson wrote: I seem to get this error "user postgres could not be created, user account already exists" when trying to install postgres. Anyone knows how to fix this? Sounds to me like the user postgres on the OS already exists. Joshua D. Drake Erik Jones wrote: Erik Jones wrote: Ok, c

[GENERAL] Fatal error while installing

I seem to get this error "user postgres could not be created, user account already exists" when trying to install postgres. Anyone knows how to fix this? Erik Jones wrote: Erik Jones wrote: Ok, consider the following table definition: CREATE TABLE stats ( id SERIAL PRIMARY KEY, hits bigint d

Re: [GENERAL] FATAL Error

"Matthew T. O'Connor" writes: > Here is what I find in pg_xlog: > [EMAIL PROTECTED] pg_xlog]# ls -l > total 114840 > -rw--- 1 postgres postgres 16777216 Aug 7 18:29 > 000100020016 So are you still getting the error? This looks like your WAL is now up to 2/16xx, so that s

Re: [GENERAL] FATAL Error

Tom Lane wrote: Matt writes: I'm getting the following error on PGSQL 8.0.8 server that I admin. I don't think this is a hardware problem but I'm not sure. Anyway in the logfile I'm constantly getting this: ERROR: xlog flush request 2/13CEA8AC is not satisfied --- flushed only to 2

Re: [GENERAL] FATAL Error

Matt writes: > I'm getting the following error on PGSQL 8.0.8 server that I admin. I > don't think this is a hardware problem but I'm not sure. Anyway in the > logfile I'm constantly getting this: > ERROR: xlog flush request 2/13CEA8AC is not satisfied --- flushed only > to 2/13634EE4 > CON

[GENERAL] FATAL Error

I'm getting the following error on PGSQL 8.0.8 server that I admin. I don't think this is a hardware problem but I'm not sure. Anyway in the logfile I'm constantly getting this: ERROR: xlog flush request 2/13CEA8AC is not satisfied --- flushed only to 2/13634EE4 CONTEXT: writing block 342

Re: [GENERAL] fatal error in pg.log

On Thu, Dec 01, 2005 at 11:18:14AM -0600, Medora Schauer wrote: > I found this in /var/log/messages: > > Dec 1 09:23:40 Qc kernel: __alloc_pages: 0-order allocation failed > (gfp=0x1d2/0) > Dec 1 09:23:40 Qc kernel: VM: killing process postmaster > > Is this because we are running out of memory

Re: [GENERAL] fatal error in pg.log

> > "Medora Schauer" <[EMAIL PROTECTED]> writes: > > I looked in the log again and sure enough I missed this immediately > > before the WARNINGS: > > > PANIC: link from /data/database/pg_xlog/000100D9 to > > /data/database/pg_xlog/000100E1 (initialization of log file 1, > > segme

Re: [GENERAL] fatal error in pg.log

"Medora Schauer" <[EMAIL PROTECTED]> writes: > I looked in the log again and sure enough I missed this immediately > before the WARNINGS: > PANIC: link from /data/database/pg_xlog/000100D9 to > /data/database/pg_xlog/000100E1 (initialization of log file 1, > segment 225) failed: N

Re: [GENERAL] fatal error in pg.log

I looked in the log again and sure enough I missed this immediately before the WARNINGS: PANIC: link from /data/database/pg_xlog/000100D9 to /data/database/pg_xlog/000100E1 (initialization of log file 1, segment 225) failed: No such file or directory LOG: server process (pid 574

Re: [GENERAL] fatal error in pg.log

"Medora Schauer" <[EMAIL PROTECTED]> writes: > We are using ver 7.3.4 (old I know but we can't upgrade until early next > year) on a linux 2.4 system and are having some flaky problems with our > apps. They just die at apparently random times. In trying to figure > out what is going on I noticed

[GENERAL] fatal error in pg.log

We are using ver 7.3.4 (old I know but we can’t upgrade until early next year) on a linux 2.4 system and are having some flaky problems with our apps.  They just die at apparently random times.  In trying to figure out what is going on I noticed a couple of messages in pg.log that concern m

Re: [GENERAL] Fatal error

On Fri, Apr 29, 2005 at 10:44:53PM -0600, [EMAIL PROTECTED] wrote: > Tom Lane wrote: > > [EMAIL PROTECTED] writes: > >> LOG: redo starts at F1/A0A4E09C > >> PANIC: Invalid page header in block 68122 of 17006 > >> LOG: startup process (pid 1959) was terminated by signal 6 > >> LOG: aborting star

Re: [GENERAL] Fatal error

Tom Lane wrote: > [EMAIL PROTECTED] writes: >> LOG: redo starts at F1/A0A4E09C >> PANIC: Invalid page header in block 68122 of 17006 >> LOG: startup process (pid 1959) was terminated by signal 6 >> LOG: aborting startup due to startup process failure > > Which PG version is this exactly? If i

Re: [GENERAL] Fatal error

[EMAIL PROTECTED] writes: > LOG: redo starts at F1/A0A4E09C > PANIC: Invalid page header in block 68122 of 17006 > LOG: startup process (pid 1959) was terminated by signal 6 > LOG: aborting startup due to startup process failure Which PG version is this exactly? If it's not the very latest in

[GENERAL] Fatal error

Hi , my server crashed this morning, aparently by a power failure, postgres refeses to start, this is the boot log LOG: database system was interrupted being in recovery at 2005-04-29 14:10:43 CST This probably means that some data blocks are corrupted and you will have to use th

Re: [GENERAL] Fatal error: Call to undefined function: pg_connect()

ar" <[EMAIL PROTECTED]> Sent: Tuesday, August 05, 2003 11:33 AM Subject: Re: [GENERAL] Fatal error: Call to undefined function: pg_connect() > shreedhar wrote: > > > > > Fatal error: Call to undefined function: pg_connect() > > This is a PHP error. Guessing you

[GENERAL] Fatal error: Call to undefined function: pg_connect()

Hi All, I updated postgre from 7.2.4 to 7.3.2 in my RHLinux7.3 system and updated current pghba.conf and postgresql.conf files as per my need. But If I try to connect through PHP which was connecting earlier with 7.2.4 is giving the following error Fatal error: Call to undefined function: pg_conn

Re: [GENERAL] Fatal error: Call to undefined function: pg_connect()

On Tuesday 05 August 2003 03:31 am, Jean-Christian Imbeault wrote: (B> shreedhar wrote: (B> > Is it necessary to uninstall previous version of PHP in my system. (B> (B> No$B!$(Bbut a new recompile will probably over-write the version you have now. (B> (B> > Which is the better compatible ve

Re: [GENERAL] Fatal error: Call to undefined function: pg_connect()

Hi did you configure php for PostgreSQL support ./configure --with-pgsql Regards Conni ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [GENERAL] fatal error - different CATALOG_VERSION_NO

>> $ Waiting for postmaster to start up...FATAL 2: database was initialized >> with CATALOG_VERSION_NO >> 200012280, >> but the backend was compiled with CATALOG_VERSION_NO 200101061. >> looks like you need to initdb. >> do i have to follow the upgrade procedures? > Yes If you're trying to sto

Re: [GENERAL] fatal error - different CATALOG_VERSION_NO

Thomas T. Thai writes: > $ Waiting for postmaster to start up...FATAL 2: database was initialized > with CATALOG_VERSION_NO > 200012280, > but the backend was compiled with CATALOG_VERSION_NO 200101061. > looks like you need to initdb. > do i have to follow the upgrade procedur