Re: [BUGS] Problem with COPY in 8.0.3
On Wed, 2005-10-12 at 19:28 -0400, Tom Lane wrote: > Oliver Elphick writes: > > On Wed, 2005-10-12 at 17:45 -0400, Tom Lane wrote: > >> Hm. Could we see the actual pg_attribute data for both this table and > >> its parent? > > > Here you are: > > Thanks. Nothing particularly strange-looking there though. Do you want > to try tracing through COPY with a debugger to see where it's getting > the bogus column order from? The problem has gone away after installation of 8.0.4, so now I can't :-( -- Oliver Elphick olly@lfix.co.uk Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA Do you want to know God? http://www.lfix.co.uk/knowing_god.html ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #1973: Error on installation after uninstall PostgreSQL
The following bug has been logged online: Bug reference: 1973 Logged by: Andri gunawan Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 Operating system: WindowsXP Pro SP2 Description:Error on installation after uninstall PostgreSQL Details: Failde to conect to database. Procedural languages files are installed, but are not activated in any databases. server closed the connection unexpectedly. This probably means the server terminated abnormally before or while processing the request. Failed to connect to database. Contrib files are instlled, but are not activated in any databases. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #1972: index error with space character
The following bug has been logged online: Bug reference: 1972 Logged by: Eduardo Soares Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Linux Fedora 4 Description:index error with space character Details: In above example the "AZTES Z" should be after the "AZTESA". It happens with any encoding type. The DB not see the space character. The index shoulb see the space and put "AZTES Z" together with "AZTES". In above list the "AZTESA" should be the first. Thanks for the help. table=# insert into edu values ('AZTES Z'); INSERT 133634 1 table=# insert into edu values ('AZTESA'); INSERT 133635 1 table=# SELECT * FROM EDU ORDER BY NOME DESC; nome --- AZTES Z AZTESA AZTES ÃNTES ANTES (8 registros) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[BUGS] BUG #1971: Start Transaction is giving Errors !!!
The following bug has been logged online: Bug reference: 1971 Logged by: Yogaraj. C Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.8 Operating system: Linux - Red Hat 9 Description:Start Transaction is giving Errors !!! Details: Hi, When I was executing the procedure (with Transaction), postgres will producing the following error. ERROR: SPI_prepare() failed on "START TRANSACTION" CONTEXT: PL/pgSQL function "sp_example1" line 4 at SQL statement If anyone know the solution for this, pleas help me. Yogaraj.C ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #1970: Existing /etc/pam.d/postgresql clobbered by RPM install
The following bug has been logged online: Bug reference: 1970 Logged by: Mark Gibson Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 Operating system: Redhat Enterprise Linux 4 Description:Existing /etc/pam.d/postgresql clobbered by RPM install Details: Hello, I noticed that when installing the 8.0.4 RPM's it replaced our existing /etc/pam.d/postgresql - this caused our system to break temporarily, as it was missing the following line: account required pam_stack.so service=system-auth I don't know whether this is required for all systems or is just a peculiarity of our setup, but could the RPM be changed to not clobber this file in the future. I believe some RPM's install conflicting configs with the .rpmnew extension. Cheers. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[BUGS] BUG #1969: Unable to Install
The following bug has been logged online: Bug reference: 1969 Logged by: jayesh Email address: [EMAIL PROTECTED] PostgreSQL version: postgresq-8.0ja Operating system: window 2000 Description:Unable to Install Details: I get following error when I click setup. Error Applying tranforms.Verify that the specified tranform paths are valid ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #1974: UTF-8 french postmaster messages corrupted
The following bug has been logged online: Bug reference: 1974 Logged by: Thomas Reiss Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 Operating system: Linux Fedora Core 1 Description:UTF-8 french postmaster messages corrupted Details: Hello, The french messages lost their accents in the latest stable release. When in 8.0.4 with $LANG=fr_FR.UTF-8, I get: [EMAIL PROTECTED] postgres]$ echo $LANG fr_FR.UTF-8 [EMAIL PROTECTED] postgres]$ pg_ctl stop en attente de l'arrêt du postmasterTRACE: arrêt en cours des traces fait postmaster arrêté When in 8.0.2, on the same server, with $LANG=fr_FR.UTF-8, I get the following, which is correct: [EMAIL PROTECTED] postgres]$ echo $LANG fr_FR.UTF-8 [EMAIL PROTECTED] postgres]$ pg_ctl stop en attente de l'arrêt du postmaster fait postmaster arrêté I did this tests in the same session, I just switch from an environnement to another by resetting the $PATH and $PGDATA environnement variables. Thanks in advance. Thomas ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] BUG #1972: index error with space character
Eduardo Soares wrote: Operating system: Linux Fedora 4 Description:index error with space character Details: In above example the "AZTES Z" should be after the "AZTESA". It happens with any encoding type. The DB not see the space character. The index shoulb see the space and put "AZTES Z" together with "AZTES". In above list the "AZTESA" should be the first. Sorting order is determined by your locale, and is different from your encoding. For example, en_GB ignores spaces but C doesn't: $ LC_COLLATE=en_GB.UTF-8 sort unsorted.txt aa a aaab aa b $ LC_COLLATE=C sort unsorted.txt aa a aa b aaab See "man locale" for details on how to find out what locales are setup on your machine. See the documentation for details on how to set locale on a database cluster. HTH -- Richard Huxton Archonet Ltd ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #1971: Start Transaction is giving Errors !!!
On Mon, Oct 17, 2005 at 12:50:29PM +0100, Yogaraj. C wrote: >When I was executing the procedure (with Transaction), postgres will > producing the following error. > > ERROR: SPI_prepare() failed on "START TRANSACTION" > CONTEXT: PL/pgSQL function "sp_example1" line 4 at SQL statement http://www.postgresql.org/docs/7.4/interactive/plpgsql-structure.html "Functions and trigger procedures are always executed within a transaction established by an outer query --- they cannot start or commit transactions" >If anyone know the solution for this, pleas help me. What problem are you trying to solve? PostgreSQL 8.0 introduced savepoints, which you can use in PL/pgSQL via an EXCEPTION clause: http://www.postgresql.org/docs/8.0/interactive/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING Another possibility might be to use dblink to make another connection to the database from within the function and execute transactions over that connection. -- Michael Fuhr ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1971: Start Transaction is giving Errors !!!
Yogaraj. C wrote: >When I was executing the procedure (with Transaction), postgres will > producing the following error. > > ERROR: SPI_prepare() failed on "START TRANSACTION" > CONTEXT: PL/pgSQL function "sp_example1" line 4 at SQL statement > >If anyone know the solution for this, pleas help me. NOTABUG. You are not allowed to use transaction commands using SPI, which in particular means PL/pgSQL. Use the EXCEPTION clause if you need a savepoint-like feature. Note that you can't close the transaction that started the function. -- Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34 "El sudor es la mejor cura para un pensamiento enfermo" (Bardia) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] BUG #1974: UTF-8 french postmaster messages corrupted
Am Dienstag, 18. Oktober 2005 15:00 schrieb Thomas Reiss: > [EMAIL PROTECTED] postgres]$ pg_ctl stop > en attente de l'arrêt du postmasterTRACE: arrêt en cours des > traces > fait > postmaster arrêté This probably means that the LC_CTYPE setting on your server does not match the database encoding. Please send us the output of SHOW lc_ctype; SHOW server_encoding; -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #1974: UTF-8 french postmaster messages corrupted
Title: RE: [BUGS] BUG #1974: UTF-8 french postmaster messages corrupted Hello Peter, On the 8.0.4 db cluster, I get the following: template1=# SHOW lc_ctype; lc_ctype - fr_FR.UTF-8 (1 ligne) Temps : 1,041 ms template1=# SHOW server_encoding; server_encoding - UNICODE (1 ligne) Temps : 0,562 ms On the 8.0.2 db cluster, I get: template1=# SHOW lc_ctype; lc_ctype - fr_FR.UTF-8 (1 ligne) Temps : 76,591 ms template1=# template1=# SHOW server_encoding; server_encoding - UNICODE (1 ligne) Temps : 0,621 ms Any clue ? > -Message d'origine- > De: Peter Eisentraut [mailto:[EMAIL PROTECTED]] > Date: mardi 18 octobre 2005 16:40 > À: REISS Thomas DSIC DESP > Cc: pgsql-bugs@postgresql.org > Objet: Re: [BUGS] BUG #1974: UTF-8 french postmaster messages > corrupted > > > Am Dienstag, 18. Oktober 2005 15:00 schrieb Thomas Reiss: > > [EMAIL PROTECTED] postgres]$ pg_ctl stop > > en attente de l'arrêt du postmasterTRACE: arrêt > en cours des > > traces > > fait > > postmaster arrêté > > This probably means that the LC_CTYPE setting on your server > does not match > the database encoding. Please send us the output of > > SHOW lc_ctype; > SHOW server_encoding; > > -- > Peter Eisentraut > http://developer.postgresql.org/~petere/ >
Re: [BUGS] BUG #1969: Unable to Install
> The following bug has been logged online: > > Bug reference: 1969 > Logged by: jayesh > Email address: [EMAIL PROTECTED] > PostgreSQL version: postgresq-8.0ja > Operating system: window 2000 > Description:Unable to Install > Details: > > I get following error when I click setup. > > Error Applying tranforms.Verify that the specified tranform > paths are valid First of all, you are aware that you're instlaling the japanese version, I hope? If so, check: 1) That you actually unpacked the whole installations before you ran it. If you just doubleclick the MSI file inside "Compressed Folder" or WinZip or whatever, it won't work. 2) That you are running on a Windows version that can actually deal with Japanese. IIRC all languages don't, but I'm not 100% sure on that. //Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1970: Existing /etc/pam.d/postgresql clobbered by
Hi, On Mon, 17 Oct 2005, Mark Gibson wrote: Bug reference: 1970 Logged by: Mark Gibson Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 Operating system: Redhat Enterprise Linux 4 Description:Existing /etc/pam.d/postgresql clobbered by RPM install Details: Hello, I noticed that when installing the 8.0.4 RPM's it replaced our existing /etc/pam.d/postgresql - this caused our system to break temporarily, as it was missing the following line: account required pam_stack.so service=system-auth I don't know whether this is required for all systems or is just a peculiarity of our setup, but could the RPM be changed to not clobber this file in the future. I believe some RPM's install conflicting configs with the .rpmnew extension. Cheers. AFAIK, RPMs look for RPM database for the existing files on the system. I think your file was not generated by any RPM, so our RPM wanted to replace it. I can't see any problems with adding account required pam_stack.so service=system-auth to our postgresql.pam file. If noone objects, we may release a new subversion of 8.0.4 with this fix (and elog patch of Tom). Regards, -- Devrim GUNDUZ Kivi Bilişim Teknolojileri - http://www.kivi.com.tr devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1970: Existing /etc/pam.d/postgresql clobbered by
Devrim GUNDUZ <[EMAIL PROTECTED]> writes: > I can't see any problems with adding > account required pam_stack.so service=system-auth See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167040 which is what inspired this to start with. Not knowing enough about PAM, I didn't get it right the first time :-( regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Fwd: [BUGS] BUG #1972: index error with space character
-- Forwarded message -- From: Eduardo RBS <[EMAIL PROTECTED]> Date: 18/10/2005 13:31 Subject: Re: [BUGS] BUG #1972: index error with space character To: Richard Huxton Hellow.. Thank you very much for the attention. I need a locate that not ignores the space chracater and also sort accents like á or ã. I made configuration using locale... see it.. Using C is almost good because it sort correctly and see the spaces.. but it does not sort the portuguese accents.. note the last two lines.. $ LC_COLLATE=C sort b.txt aa a aa z aaaz aaz eado eza édina émaster and with the "my" locale pt_BR it sort correctly the accents but ignores the space chracater LC_COLLATE=pt_BR.utf8 sort b.txt aa a aaab aaaz aaz aa z eado édina émaster eza What i need should a merge of C and pt_BR.. i mean.. a locale that see the spaces like C but sort accents like pt_BR.. I tried several others locales.. and only C see the space character. Thanks for the attention. -- []'s Eduardo RBS http://linuxstok.sourceforge.net 2005/10/18, Richard Huxton : > Eduardo Soares wrote: > > Operating system: Linux Fedora 4 > > Description:index error with space character > > Details: > > > > In above example the "AZTES Z" should be after the "AZTESA". It happens with > > any encoding type. The DB not see the space character. The index shoulb see > > the space and put "AZTES Z" together with "AZTES". In above list the > > "AZTESA" should be the first. > > Sorting order is determined by your locale, and is different from your > encoding. For example, en_GB ignores spaces but C doesn't: > > $ LC_COLLATE=en_GB.UTF-8 sort unsorted.txt > aa a > > aaab > aa b > > $ LC_COLLATE=C sort unsorted.txt > aa a > aa b > > aaab > > See "man locale" for details on how to find out what locales are setup > on your machine. See the documentation for details on how to set locale > on a database cluster. > > HTH > -- >Richard Huxton >Archonet Ltd > -- []'s Eduardo RBS http://linuxstok.sourceforge.net ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG #1975: Postgres 8.0.4 build fails on AIX
The following bug has been logged online: Bug reference: 1975 Logged by: Dirk Pirschel Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.4 Operating system: AIX Description:Postgres 8.0.4 build fails on AIX Details: Postgres 8.0.4 build fails on AIX. $cd /var/tmp/postgresql-8.0.4 $./configure --prefix=$HOME/software # [no errors] $gmake touch libpq.a ../../../src/backend/port/aix/mkldexport.sh libpq.a > libpq.exp gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels -fno-strict-aliasing -Wl,-bnoentry -Wl,-H512 -Wl,-bM:SRE -o libpq.so libpq.a -L../../../src/port -L/client/lib -L../../../src/port -L/client/lib -lnsl -Wl,-bI:../../../src/backend/postgres.imp -Wl,-bE:libpq.exp ld: 0711-224 WARNING: Duplicate symbol: .pqStrerror ld: 0711-224 WARNING: Duplicate symbol: .pqGetpwuid ld: 0711-224 WARNING: Duplicate symbol: .getnameinfo_all ld: 0711-224 WARNING: Duplicate symbol: .getaddrinfo_all ld: 0711-224 WARNING: Duplicate symbol: .freeaddrinfo_all ld: 0711-224 WARNING: Duplicate symbol: .rangeSockAddr ld: 0711-224 WARNING: Duplicate symbol: .SockAddr_cidr_mask ld: 0711-224 WARNING: Duplicate symbol: .promote_v4_to_v6_addr ld: 0711-224 WARNING: Duplicate symbol: .promote_v4_to_v6_mask ld: 0711-224 WARNING: Duplicate symbol: .pqsignal ld: 0711-224 WARNING: Duplicate symbol: .pg_char_to_encoding ld: 0711-224 WARNING: Duplicate symbol: .pg_valid_client_encoding ld: 0711-224 WARNING: Duplicate symbol: .pg_valid_server_encoding ld: 0711-224 WARNING: Duplicate symbol: .pg_char_to_encname_struct ld: 0711-224 WARNING: Duplicate symbol: .pg_encoding_to_char ld: 0711-224 WARNING: Duplicate symbol: pg_encname_tbl ld: 0711-224 WARNING: Duplicate symbol: pg_encname_tbl_sz ld: 0711-224 WARNING: Duplicate symbol: pg_enc2name_tbl ld: 0711-224 WARNING: Duplicate symbol: .pg_strcasecmp ld: 0711-224 WARNING: Duplicate symbol: .pg_strncasecmp ld: 0711-224 WARNING: Duplicate symbol: .pg_toupper ld: 0711-224 WARNING: Duplicate symbol: .pg_tolower ld: 0711-224 WARNING: Duplicate symbol: .pg_encoding_mblen ld: 0711-224 WARNING: Duplicate symbol: .pg_utf_mblen ld: 0711-224 WARNING: Duplicate symbol: .pg_mule_mblen ld: 0711-224 WARNING: Duplicate symbol: .pg_mic_mblen ld: 0711-224 WARNING: Duplicate symbol: .pg_encoding_dsplen ld: 0711-224 WARNING: Duplicate symbol: .pg_encoding_max_length ld: 0711-224 WARNING: Duplicate symbol: pg_wchar_table ld: 0711-224 WARNING: Duplicate symbol: pg_utf_mblen ld: 0711-224 WARNING: Duplicate symbol: pg_mule_mblen ld: 0711-224 WARNING: Duplicate symbol: .pg_set_noblock ld: 0711-224 WARNING: Duplicate symbol: .pg_set_block ld: 0711-224 WARNING: Duplicate symbol: .EncryptMD5 ld: 0711-224 WARNING: Duplicate symbol: .md5_hash ld: 0711-224 WARNING: Duplicate symbol: lo_open ld: 0711-224 WARNING: Duplicate symbol: .lo_close ld: 0711-224 WARNING: Duplicate symbol: .lo_read ld: 0711-224 WARNING: Duplicate symbol: .lo_write ld: 0711-224 WARNING: Duplicate symbol: .lo_lseek ld: 0711-224 WARNING: Duplicate symbol: .lo_creat ld: 0711-224 WARNING: Duplicate symbol: .lo_tell ld: 0711-224 WARNING: Duplicate symbol: .lo_unlink ld: 0711-224 WARNING: Duplicate symbol: .lo_import ld: 0711-224 WARNING: Duplicate symbol: .lo_export ld: 0711-224 WARNING: Duplicate symbol: lo_close ld: 0711-224 WARNING: Duplicate symbol: lo_read ld: 0711-224 WARNING: Duplicate symbol: lo_write ld: 0711-224 WARNING: Duplicate symbol: lo_lseek ld: 0711-224 WARNING: Duplicate symbol: lo_creat ld: 0711-224 WARNING: Duplicate symbol: lo_tell ld: 0711-224 WARNING: Duplicate symbol: lo_unlink ld: 0711-224 WARNING: Duplicate symbol: lo_import ld: 0711-224 WARNING: Duplicate symbol: lo_export ld: 0711-224 WARNING: Duplicate symbol: pqsignal ld: 0711-224 WARNING: Duplicate symbol: md5_hash ld: 0711-224 WARNING: Duplicate symbol: EncryptMD5 ld: 0711-224 WARNING: Duplicate symbol: getaddrinfo_all ld: 0711-224 WARNING: Duplicate symbol: freeaddrinfo_all ld: 0711-224 WARNING: Duplicate symbol: getnameinfo_all ld: 0711-224 WARNING: Duplicate symbol: rangeSockAddr ld: 0711-224 WARNING: Duplicate symbol: SockAddr_cidr_mask ld: 0711-224 WARNING: Duplicate symbol: promote_v4_to_v6_addr ld: 0711-224 WARNING: Duplicate symbol: promote_v4_to_v6_mask ld: 0711-224 WARNING: Duplicate symbol: pg_mic_mblen ld: 0711-224 WARNING: Duplicate symbol: pg_encoding_mblen ld: 0711-224 WARNING: Duplicate symbol: pg_encoding_dsplen ld: 0711-224 WARNING: Duplicate symbol: pg_encoding_max_length ld: 0711-224 WARNING: Duplicate symbol: pg_valid_client_encoding ld: 0711-224 WARNING: Duplicate symbol: pg_valid_server_encoding ld: 0711-224 WARNING: Duplicate symbol: pg_char_to_encname_struct ld: 0711-224 WARNING: Duplicate symbol: pg_char_to_encoding ld: 0711-224 WARNING: Duplicate symbol: pg_encoding_to_char ld: 0711-224 WARNING: Duplicate symbol: pg_set_noblock ld: 0711-224 WARNING: Duplicate symbol: pg_set_block ld: 0711-224 WARNING: Duplicate symbol: pg_strcasecmp ld: 0711-224 WARNING: Duplicate symbol: pg_strncasecmp ld:
Re: Fwd: [BUGS] BUG #1972: index error with space character
Eduardo RBS <[EMAIL PROTECTED]> writes: > I need a locate that not ignores the space chracater and also sort > accents like á or ã. I'm afraid you'll have to learn how to build your own locale definition. AFAIK, the "C" locale is the *only* common locale in which spaces aren't second-class citizens. I know that it is possible to write your own locale definition, but this is not the place to ask about how. Try a glibc support forum. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster