[BUGS] BUG #3986: Error ts_vector with UTF8 WS2003
The following bug has been logged online: Bug reference: 3986 Logged by: Yann Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.0 build1400 Operating system: Windows Server 2003 Description:Error ts_vector with UTF8 WS2003 Details: Hi, When i try to execute the ts_vector function with a text i get the following error : ERROR: 22021: invalid byte sequence for encoding UTF8: 0xc3 I've tried with a lot of different text, the error is always the same. On a WINXP OS it works fine. I've seen the same bug reported in your newsgroup : BUG #3766 Thanks, -- Yann ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #3979: SELECT DISTINCT slow even on indexed column
On Thu, 2008-02-21 at 23:34 +, David Lee wrote: I ran EXPLAIN and it showed that the path did not use the index, so I ran: Your expectation that this would use an index is unfortunately not correct. We need to check visibility on the table rows to do the query. We choose to do this by doing a sort and then a unique operation. That's the most efficient plan when there are potentially many unique values. In the case you mention it would be faster for us to skip through the index retrieving at most one row from each value in the index. We don't currently do that, but we could. However that plan would be restricted only to queries of the form SELECT DISTINCT column-list-of-index FROM table; so its probably not going to be optimised anytime soon. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---(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] Incomplete docs for restore_command for hot standby
2008/2/22, Simon Riggs [EMAIL PROTECTED]:
On Thu, 2008-02-21 at 08:01 +0600, Markus Bertheau wrote:
Section 24.3.3.1 states about restore_command:
The command will be asked for file names that are not present in the
archive; it must return nonzero when so asked.
Section 24.4.1 further states:
The magic that makes the two loosely coupled servers work together is
simply a restore_command used on the standby that waits for the next
WAL file to become available from the primary.
It is not clear from the first paragraph, whether the non-existing
file that restore_command is being asked for is a not-yet-generated
WAL file or something different. If it was a not-yet-generated WAL
file, restore_command for replication would have to wait for it to
appear. If it was something different, restore_command for replication
would have to return an error right away. (Because else it would hang
indefinitely, waiting for a file that is not going to appear). Yet I
couldn't find hints in the documentation as to how these two cases can
be detected by restore_command, i.e. how restore_command should tell a
request for a WAL file from a request for a non-WAL file.
The two sentences aren't mutually exclusive, especially when you
consider they are discussing two different use cases. Why not read up on
pg_standby anyway?
I read about pg_standby, but this is not about solving a particular problem but
about missing information in the docs.
Practice (http://archives.postgresql.org/sydpug/2006-10/msg1.php)
shows that this is a problem, and people use unproved heuristics
('history' substring in the requested file name).
Old email written during beta. Read at your own peril.
The email may be old, but the problem at hand is still relevant.
Additionally, 24.3.3 contains slightly misleading information:
It is important that the command return nonzero exit status on
failure. The command will be asked for log files that are not present
in the archive; it must return nonzero when so asked. This is not an
error condition.
This suggests that all non-existing files that restore_command will be
asked for are log files. One could therefore reasonably assume that
restore_command for replication should wait on all non-existing files.
24.3.3.1 later corrects this by stating that not only log files may be
requested, but nevertheless.
If you have some suggested changes, I'd be happy to hear them.
Probably additions are better than just changes though.
What about this:
*** a/doc/src/sgml/backup.sgml
--- b/doc/src/sgml/backup.sgml
***
*** 1001,1011 restore_command = 'cp /mnt/server/archivedir/%f %p'
para
It is important that the command return nonzero exit status on failure.
! The command emphasiswill/ be asked for log files that are not present
! in the archive; it must return nonzero when so asked. This is not an
! error condition. Be aware also that the base name of the literal%p/
! path will be different from literal%f/; do not expect them to be
! interchangeable.
/para
para
--- 1001,1011
para
It is important that the command return nonzero exit status on failure.
! The command emphasiswill/ be asked for log and other files that are
! not present in the archive; it must return nonzero when so asked. This is
! not an error condition. Be aware also that the base name of the
! literal%p/ path will be different from literal%f/; do not expect
! them to be interchangeable.
/para
para
***
*** 1576,1594 archive_command = 'local_backup_script.sh'
para
The magic that makes the two loosely coupled servers work together is
! simply a varnamerestore_command/ used on the standby that waits
! for the next WAL file to become available from the primary. The
! varnamerestore_command/ is specified in the
filenamerecovery.conf/ file on the standby server. Normal recovery
processing would request a file from the WAL archive, reporting failure
if the file was unavailable. For standby processing it is normal for
! the next file to be unavailable, so we must be patient and wait for
! it to appear. A waiting varnamerestore_command/ can be written as
! a custom script that loops after polling for the existence of the next
! WAL file. There must also be some way to trigger failover, which should
! interrupt the varnamerestore_command/, break the loop and return
! a file-not-found error to the standby server. This ends recovery and
! the standby will then come up as a normal server.
/para
para
--- 1576,1596
para
The magic that makes the two loosely coupled servers work together is
! simply a varnamerestore_command/ used on the standby that, when asked
! for the a WAL file, waits for it to become available from
[BUGS] BUG #3987: Not checking the password
The following bug has been logged online: Bug reference: 3987 Logged by: chandra Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Linux Description:Not checking the password Details: We have installed postgres in Linux box and accessing through Pgadmin 3-1.8.2.2. When we connecting to the database it is asking the password. Without giving the password we are able to connect to the database thru pqadmin tool. It should check the password. Am I missing while installing postgres? We are storing very confidential data in our database. If anyone knows the ip address they can easly connect thru pgadmin and hack the data. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #3988: problem with installation
The following bug has been logged online: Bug reference: 3988 Logged by: Amandeep Singh Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.0 Operating system: Windows XP SP-2 Description:problem with installation Details: I downloaded Postgresql 8.3.0 and tried to install it. In the final step before reaching the finish stage, it showed the message Problem during installation on trying again, it showed the message User already exists again and again i tried to uninstall it, but it wasn't installed at all please help me out ---(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 #3989: Error when Installing
The following bug has been logged online: Bug reference: 3989 Logged by: Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3 Release Operating system: Vista Description:Error when Installing Details: When trying to install the new release of Postgres 8.3 I'm getting this error: Failed to run initdb: 1! Please see the logfile in 'C:\Program Files\PostgreSQL\8.3RC2\tmp \initdb.log' Note! You must read/copy this logfile before you click OK, or it will be automatically removed. Previous versions of Postgres install fine. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
On Sun, Feb 24, 2008 at 12:11 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: Hi Dave, Please find the attached files - log in ZIP format and the messages from MessageBox-es (JPG files). Hi Miro, I don't see why that error would occur unless there's a tmp file in C:\Program Files\PostgreSQL\8.3 already. I assume thats not the case? Magnus; any ideas? To get up and running though, you should be able to install with initdb disabled and then run it manually from the commandline. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
Can you send me a script (BAT/CMD) file? Or another installations where more detail log is available? Miro. Dave Page wrote: On Sun, Feb 24, 2008 at 12:11 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: Hi Dave, Please find the attached files - log in ZIP format and the messages from MessageBox-es (JPG files). Hi Miro, I don't see why that error would occur unless there's a tmp file in C:\Program Files\PostgreSQL\8.3 already. I assume thats not the case? Magnus; any ideas? To get up and running though, you should be able to install with initdb disabled and then run it manually from the commandline.
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
On Mon, Feb 25, 2008 at 2:48 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: Can you send me a script (BAT/CMD) file? Or another installations where more detail log is available? Script for what? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [BUGS] BUG #3987: Not checking the password
chandra [EMAIL PROTECTED] writes: When we connecting to the database it is asking the password. Without giving the password we are able to connect to the database thru pqadmin tool. It should check the password. It sounds like you have different authentication methods selected for different connection sources. Look at pg_hba.conf (and don't forget you need pg_ctl reload after changing it). regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
To get up and running though, you should be able to install with initdb disabled and then run it manually from the commandline. How to do the above? Miro. Dave Page wrote: On Mon, Feb 25, 2008 at 2:48 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: Can you send me a script (BAT/CMD) file? Or another installations where more detail log is available? Script for what?
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
On Mon, Feb 25, 2008 at 3:39 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: To get up and running though, you should be able to install with initdb disabled and then run it manually from the commandline. How to do the above? When you install, un-check the initdb option on the initdb page of the wizard. Then, initialise the cluster after installation by running a command like: initdb -D ../data from the PostgreSQL command prompt window (there's a shortcut on the start menu). See http://www.postgresql.org/docs/8.3/interactive/app-initdb.html for more info on the initdb options. Once that's done you should register PostgreSQL as a service - see the 'register' mode of pg_ctl: http://www.postgresql.org/docs/8.3/interactive/app-pg-ctl.html Those steps are roughly what the installer normally does for you. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
I can not start that command because: C:\Program Files\PostgreSQL\8.3\bininitdb -D ../data The program "postgres" is needed by initdb but was not found in the same directory as "C:\Program Files\PostgreSQL\8.3\bin/initdb". Check your installation. In the same time there are 2 files with that name: C:\Program Files\PostgreSQL\8.3\bindir postgres.* Volume in drive C is ACER Volume Serial Number is 7C12-D67C Directory of C:\Program Files\PostgreSQL\8.3\bin 01.02.2008 . 04:00 . 3661824 postgres.exe 01.02.2008 . 04:00 . 1092970 postgres.lib 2 File(s) 4754794 bytes 0 Dir(s) 110786924544 bytes free Miro. Dave Page wrote: On Mon, Feb 25, 2008 at 3:39 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: To get up and running though, you should be able to install with initdb disabled and then run it manually from the commandline. How to do the above? When you install, un-check the initdb option on the initdb page of the wizard. Then, initialise the cluster after installation by running a command like: initdb -D ../data from the PostgreSQL command prompt window (there's a shortcut on the start menu). See http://www.postgresql.org/docs/8.3/interactive/app-initdb.html for more info on the initdb options. Once that's done you should register PostgreSQL as a service - see the 'register' mode of pg_ctl: http://www.postgresql.org/docs/8.3/interactive/app-pg-ctl.html Those steps are roughly what the installer normally does for you.
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
On Mon, Feb 25, 2008 at 4:56 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: I can not start that command because: C:\Program Files\PostgreSQL\8.3\bininitdb -D ../data The program postgres is needed by initdb but was not found in the same directory as C:\Program Files\PostgreSQL\8.3\bin/initdb. Check your installation. In the same time there are 2 files with that name: C:\Program Files\PostgreSQL\8.3\bindir postgres.* Volume in drive C is ACER Volume Serial Number is 7C12-D67C Directory of C:\Program Files\PostgreSQL\8.3\bin 01.02.2008 г. 04:00 ч. 3 661 824 postgres.exe 01.02.2008 г. 04:00 ч. 1 092 970 postgres.lib 2 File(s) 4 754 794 bytes 0 Dir(s) 110 786 924 544 bytes free Thats the bug fixed in my recent patch that I mentioned. Use a user account other than Administrator and it should work. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[BUGS] BUG #3990: PostgreSQL does not work
The following bug has been logged online: Bug reference: 3990 Logged by: Rafael Aguilar Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Windows vista 32 bits Description:PostgreSQL does not work Details: The PostgreSQL 8.0 does not work with Windows Vista 32 bits. Is it a trick to install? , what should I do?, the newer version of the software (8.3) works? ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
Hi, When I see the error I suppose that the kind of the problem is space in the path: "C:\Program Files\PostgreSQL\8.3\bin". Then I use another program path without space and the installation is successful. I mean the regular installation, not patched. Regards, Miro. Miroslav Nachev wrote: For the current case is used user "miro" with administrator rights. You suggest me to remove administrator rights? Miro. Dave Page wrote: On Mon, Feb 25, 2008 at 4:56 PM, Miroslav Nachev [EMAIL PROTECTED] wrote: I can not start that command because: C:\Program Files\PostgreSQL\8.3\bininitdb -D ../data The program "postgres" is needed by initdb but was not found in the same directory as "C:\Program Files\PostgreSQL\8.3\bin/initdb". Check your installation. In the same time there are 2 files with that name: C:\Program Files\PostgreSQL\8.3\bindir postgres.* Volume in drive C is ACER Volume Serial Number is 7C12-D67C Directory of C:\Program Files\PostgreSQL\8.3\bin 01.02.2008 г. 04:00 ч. 3 661 824 postgres.exe 01.02.2008 г. 04:00 ч. 1 092 970 postgres.lib 2 File(s) 4 754 794 bytes 0 Dir(s) 110 786 924 544 bytes free Thats the bug fixed in my recent patch that I mentioned. Use a user account other than Administrator and it should work.
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
2008/2/25 Miroslav Nachev [EMAIL PROTECTED]: Hi, When I see the error I suppose that the kind of the problem is space in the path: C:\Program Files\PostgreSQL\8.3\bin. Then I use another program path without space and the installation is successful. I mean the regular installation, not patched. Sorry, you mean the installer works completely, including the initdb steps if you use a path containing no spaces? That's just bizarre - there are thousands, probably hundreds of thousands of working installations in paths containing spaces. I've done hundreds myself! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #3990: PostgreSQL does not work
Rafael Aguilar wrote: The PostgreSQL 8.0 does not work with Windows Vista 32 bits. 8.0 is 3 years old (compare Vista: 1 year) and deprecated on Windows. Use something newer. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #3980: Can not Install PostgreSQL - error at the end of installation
Yes, this is curious for me also. Miro. On 2/25/08, Dave Page [EMAIL PROTECTED] wrote: 2008/2/25 Miroslav Nachev [EMAIL PROTECTED]: Hi, When I see the error I suppose that the kind of the problem is space in the path: C:\Program Files\PostgreSQL\8.3\bin. Then I use another program path without space and the installation is successful. I mean the regular installation, not patched. Sorry, you mean the installer works completely, including the initdb steps if you use a path containing no spaces? That's just bizarre - there are thousands, probably hundreds of thousands of working installations in paths containing spaces. I've done hundreds myself! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Oracle-compatible database company
Re: [BUGS] BUG #3986: Error ts_vector with UTF8 WS2003
Yann wrote: When i try to execute the ts_vector function with a text i get the following error : ERROR: 22021: invalid byte sequence for encoding UTF8: 0xc3 It seems to be a client encoding problem. What is your client_encoding? A common problem is a mismatch between client_encoding and the terminal or application encoding. -- Euler Taveira de Oliveira http://www.timbira.com/ ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
