[BUGS] BUG #1271: Installation problems (cannot execute initdb.exe)
The following bug has been logged online: Bug reference: 1271 Logged by: Ramzi Fadel Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Windows XP Prof, 5.1.2600 Build 2600 Description:Installation problems (cannot execute initdb.exe) Details: The installation file: postgresql-8.0-beta2-dev3.msi Error log; see below. Steps taken: - Run the installation with a administrator user (I do expect the installation to complete!) - The installation creates an user for the service named "postrunner" - Log off - Log in with the "postrunner" user - Run the installation. The installation fails during creation of the cluster, see below: --- Initdb.log: --- The files belonging to this database system will be owned by user "raf". This user must also own the server process. The database cluster will be initialized with locale C. fixing permissions on existing directory C:/PGSQL80/data ... ok creating directory C:/PGSQL80/data/global ... ok creating directory C:/PGSQL80/data/pg_xlog ... ok creating directory C:/PGSQL80/data/pg_xlog/archive_status ... ok creating directory C:/PGSQL80/data/pg_clog ... ok creating directory C:/PGSQL80/data/pg_subtrans ... ok creating directory C:/PGSQL80/data/base ... ok creating directory C:/PGSQL80/data/base/1 ... ok creating directory C:/PGSQL80/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in C:/PGSQL80/data/base/1 ... execution of PostgreSQL by a user with administrative permissions is not permitted. The server must be started under an unprivileged user ID to prevent possible system security compromise. See the documentation for more information on how to properly start the server. child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "C:/PGSQL80/data" ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG #1272: text + numeric wrong behaviour
The following bug has been logged online:
Bug reference: 1272
Logged by: Damjan Pipan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.2
Operating system: linux 2.4
Description:text + numeric wrong behaviour
Details:
CREATE TABLE a1(
description text,
amount numeric(9,2)
);
INSERT INTO a1 VALUES ('asdasd', 370);
SELECT * FROM a1;
SELECT description::varchar, amount FROM a1;
first select does not return amount, second does.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Re: [BUGS] BUG #1271: Installation problems (cannot execute initdb.exe)
> Steps taken: > - Run the installation with a administrator user (I do expect > the installation to complete!) It should be complete once that is done. > - The installation creates an user for the service named "postrunner" > - Log off > - Log in with the "postrunner" user > - Run the installation. The installation fails during > creation of the cluster, see below: You shouldn't need to perform these two last steps. The installation is complete once the Windows Installer sequence is done. > --- > Initdb.log: > --- > The files belonging to this database system will be owned by > user "raf". This means you have run initdb as "raf", not as "postrunner". ANd "raf" is a local administrator on the machine. The installer will run initdb with the account specifeid as the service user. If you need to run initdb manually, you should do this with that same account, which must not be an administrator. //Magnus ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] BUG #1266: Improper unique constraint / MVCCactivitieswithin
On Wed, 29 Sep 2004, Aleksey Fedorchenko wrote: > > IIRC, b2 was before Tom changed the code for doing triggers between > > function statements, current sources have that code. So, b3 should have > > the change I mentioned which makes the above work (for immediate > > constraints). > > You're right! > Cases 2 and 3 are processed correctly by b3. Thanks a lot for support. > > PS: Do you know when developers team plans to fix case 1 issue? Not really. It's been a known issue for a while, but I don't think anyone's come up with a good attack plan. We could always use help. ;) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] BUG #1272: text + numeric wrong behaviour
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > first select does not return amount, second does. Huh? I get regression=# SELECT * FROM a1; description | amount -+ asdasd | 370.00 (1 row) regression=# SELECT description::varchar, amount FROM a1; description | amount -+ asdasd | 370.00 (1 row) on both 7.3 and current ... regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] BUG #1273: bad path for english.stop in tsearch2
The following bug has been logged online: Bug reference: 1273 Logged by: Werner Bohl Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Windows XP pro Description:bad path for english.stop in tsearch2 Details: Running Postgresql 8.0beta2-dev3. When issuing a query using tsearch2. It erred, looking for english.stop in /usr/local/psql/share/contrib. Fixed creating that directory structure and placing english.stop there, but it should look for that file under Program Files/PostgreSQL/8.0-beta2-dev3/share/contrib. ---(end of broadcast)--- TIP 8: explain analyze is your friend
[BUGS] BUG #1274: Trigger sequence incorrect
The following bug has been logged online: Bug reference: 1274 Logged by: shancheng Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Fedora 2 Description:Trigger sequence incorrect Details: The problem happens when I was trying the example that is described in "PostgreSQL 8.0.0beta1 Documentation, chapt 33.4 --- A Complete Example". At the last step, as the document says, the result should be: => DELETE FROM ttest; INFO: trigf (fired before): there are 2 rows in ttest INFO: trigf (fired after ): there are 1 rows in ttest INFO: trigf (fired before): there are 1 rows in ttest INFO: trigf (fired after ): there are 0 rows in ttest DELETE 2 But what i see is that: test=# DELETE FROM ttest; NOTICE: trigf (fired before): there are 2 tuples in ttest NOTICE: trigf (fired before): there are 1 tuples in ttest NOTICE: trigf (fired after ): there are 0 tuples in ttest NOTICE: trigf (fired after ): there are 0 tuples in ttest DELETE 2 The execution sequence of the triggers is incorrect. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
