[BUGS] BUG Postgresql 7.4.6 : usecreatedb flag
Hi, This bug (I suppose it's a bug) is very simple. Fedora Core 3/postgresql-7.4.6-1.FC3.2 su - postgres createuser pguser Answer yes and no so pguser can create db but can't create new user psql template1 template1=# select * from pg_shadow; usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | valuntil | useconfig --+--+-+--+---+ +--+--- postgres |1 | t | t| t || | pguser | 100 | f | f| f || | (2 lignes) The flag in usecreatedb's column is false instead of true ! Regards, Stephane PS : same behaviour with FC2/postgresql-7.4.6-1.FC2.2. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] [pgsql-www] BUG #1355: 8.0.0 rc2 installer fails
The following bug has been logged online: Bug reference: 1355 Logged by: Scott Stillwell Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Windows XP Pro SP2 Description:8.0.0 rc2 installer fails Details: When installing PostgreSQL 8.0.0 rc2 on my computer (Windows XP Professional, SP2 and all current patches), I accepted all defaults (with the exception of assigning a password to the local Windows account and the postgres password). I get the following error near the end of the process: Failed to run initdb: -1073741512! Please see the logfile in 'C:\Program Files\PostgreSQL\8.0.0-rc2\tmp\initdb.log'. Note! You must read/copy this logfile before you click OK, or it will be automatically removed. While the dialog box is still displayed, I checked the initdb.log file. It is zero bytes with no contents. After clicking OK, the installer rolls back, at which point I get another dialog titled "Fatal Error" saying Installation ended prematurely because of an error. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] postgresql-8.0.0 beta5 & postgresql-7.4.6 can't compile
Hi, Bruce,
Good news is that I've found that the reason caused the compilation
error messages about signal.h header file I reported to you before - I
used GCC binary built on Solaris 9 x86,which has old header files to
work with. The error got fixed after using the gcc binary for Solaris 10
x86.
However, I got the new error messages when building Postgres 8.0 on
Solaris 10 x86, the error is as the following:
--
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../../src/include -c -o heaptuple.o
heaptuple.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../../src/include -c -o indextuple.o
indextuple.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../../src/include -c -o indexvalid.o
indexvalid.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../../src/include -c -o printtup.o
printtup.c
printtup.c:656: error: parse error before "message"
printtup.c:660: error: parse error before '&' token
printtup.c:660: warning: type defaults to `int' in declaration of
`pq_sendint'
printtup.c:660: error: conflicting types for `pq_sendint'
../../../../src/include/libpq/pqformat.h:25: error: previous declaration
of `pq_sendint'
printtup.c:660: warning: data definition has no type or storage class
printtup.c:672: warning: type defaults to `int' in declaration of `origattr'
printtup.c:672: error: conflicting types for `origattr'
printtup.c:668: error: previous declaration of `origattr'
printtup.c:672:46: warning: null character(s) ignored
printtup.c:672: confused by earlier errors, bailing out
make[4]: *** [printtup.o] Error 1
make[4]: Leaving directory
`/tests/postgres/postgresql-7.4.6/src/backend/access/common'
make[3]: *** [common-recursive] Error 2
make[3]: Leaving directory
`/tests/postgres/postgresql-7.4.6/src/backend/access'
make[2]: *** [access-recursive] Error 2
make[2]: Leaving directory `/tests/postgres/postgresql-7.4.6/src/backend'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tests/postgres/postgresql-7.4.6/src'
make: *** [all] Error 2
--
Could you please let me know why the above error happened when running
make, and how to solve it?
Thanks in advance for your help!
Happy holiday,
Jenny
Luojia Chen wrote:
> Bruce Momjian wrote:
>
>>Luojia Chen wrote:
>>
>>
>>>Hi,
>>>
>>>Please see my inline reply.
>>>
>>>Bruce Momjian wrote:
>>>
>>>
Would you tell use what is on this line?
/usr/include/sys/siginfo.h:259:
>>>
>>>ctid_t __ctid; /* contract ID */
>>
>>
>>OK, do a 'grep' and find out what /usr/include/* file contains the
>>definiation of ctid_t.
>
>
> Hi,Bruce,
>
> The ctid_t was defined in /usr/include/sys/types.h
>
> typedef id_tctid_t;
>
>
Seems you need an extra #include for that platform. Try adding
"#include " before the signal.h include and see if that
helps.
>>>
>>>Adding the "#include " in the "/usr/include/sys/signal.h"
>>>and "/usr/include/signal.h" doesn't help.
>>
>>
>>OK.
>>
>>
>>
If your signal.h can't be used without a previous include being present
it sounds like a bug in the operating system.
My BSD system has for the signal manual page:
#include
void
*signal(sig, func());
Does your signal manual page have another #include at the top?
>>>
>>>No, I didn't see any other #include at the top for the manual page
>>>It shows as:
>>>---
>>> #include
>>>
>>>void (*signal (int sig, void (*disp)(int)))(int);
>>
>>
>>OK, try a simple test. Create a small C file that just includes
>>signal.h and see if it compiles. If it doesn't, that manual page is
>>wrong, at the least.
>>
>
>
> A simple test.c as bellow as you suggested:
>
> #include
> #include
>
> int main()
> {
> printf("just a test");
> return 0;
> }
>
> It compiled and run well without any error.
>
>
>
> Thanks,
> Jenny
>
>
>
>
--
Jenny Chen
Software Engineer
Market Development Engineering
v-mail:(510) 574-7149
SUN Microsystems
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Re: [BUGS] [pgsql-www] BUG #1355: 8.0.0 rc2 installer fails
I assume the script is broken..._I_ sure didn't send it to -www :) No, no real lockdown except for the Windows Firewall that installs with SP2, but it didn't complain or offer to block or unblock as usual. The postgres account that it created was granted the 'logon as a service' right, but I haven't checked permissions...what directories would it need access to beyond its own tree? Special permissions beyond "logon as a service"? I will retry the install and check the initdb.bat file for paths. The Application event log contains two messages for each attempted install. The first error nearly mirrors the displayed error: Product: PostgreSQL 8.0.0-rc2 -- Failed to run initdb: -1073741512! Please see the logfile in 'C:\Program Files\PostgreSQL\8.0.0-rc2\tmp\initdb.log'. Note! You must read/copy this logfile before you click OK, or it will be automatically removed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. The second message is informational and is as follows: Product: PostgreSQL 8.0.0-rc2 -- Installation failed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. No further information is in the System or Security event logs. Thanks for the reply...I'll forward more information as I acquire it. Regards, Scott Stillwell -Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: Thursday, December 23, 2004 3:00 AM To: Scott Stillwell; [EMAIL PROTECTED]; pgsql-bugs@postgresql.org Subject: RE: [pgsql-www] BUG #1355: 8.0.0 rc2 installer fails (um, why was this filed to -www? Copying over to -bugs where it should be. Something wrong with the scripts, I assume) > The following bug has been logged online: > > Bug reference: 1355 > Logged by: Scott Stillwell > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0 > Operating system: Windows XP Pro SP2 > Description:8.0.0 rc2 installer fails > Details: > > When installing PostgreSQL 8.0.0 rc2 on my computer (Windows XP > Professional, SP2 and all current patches), I accepted all defaults > (with the exception of assigning a password to the local Windows > account and the postgres password). I get the following error near > the end of the process: > > Failed to run initdb: -1073741512! > Please see the logfile in 'C:\Program > Files\PostgreSQL\8.0.0-rc2\tmp\initdb.log'. > Note! You must read/copy this logfile before you click OK, or it will > be automatically removed. > > While the dialog box is still displayed, I checked the initdb.log > file. It is zero bytes with no contents. > > After clicking OK, the installer rolls back, at which point I get > another dialog titled "Fatal Error" saying > > Installation ended prematurely because of an error. Very interesting error :-) That means the initdb process exited with an error code that certainly didn't come from initdb... Have you installed any non-standard security products, or done any lockdown from the standard level of the system? So that perhaps the postgres account doesn't have access to required DLL files? Also, when this happens, can you check the contents of 8.0.0-rc2\tmp\initdb.bat and see if the paths entered there are correct? Finally, do you get anything in the windows event logs when this happens? //Magnus ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] [pgsql-www] BUG #1355: 8.0.0 rc2 installer fails
Found the problem...it's been reported before. http://archives.postgresql.org/pgsql-bugs/2004-11/msg00195.php I was a bad boy and left off the part about the missing ordinal in libeay32.dll... Dunno if that's something that still needs to be fixed, but at least I've got a workaround. Scott -Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: Thursday, December 23, 2004 3:00 AM To: Scott Stillwell; [EMAIL PROTECTED]; pgsql-bugs@postgresql.org Subject: RE: [pgsql-www] BUG #1355: 8.0.0 rc2 installer fails (um, why was this filed to -www? Copying over to -bugs where it should be. Something wrong with the scripts, I assume) > The following bug has been logged online: > > Bug reference: 1355 > Logged by: Scott Stillwell > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0 > Operating system: Windows XP Pro SP2 > Description:8.0.0 rc2 installer fails > Details: > > When installing PostgreSQL 8.0.0 rc2 on my computer (Windows XP > Professional, SP2 and all current patches), I accepted all defaults > (with the exception of assigning a password to the local Windows > account and the postgres password). I get the following error near > the end of the process: > > Failed to run initdb: -1073741512! > Please see the logfile in 'C:\Program > Files\PostgreSQL\8.0.0-rc2\tmp\initdb.log'. > Note! You must read/copy this logfile before you click OK, or it will > be automatically removed. > > While the dialog box is still displayed, I checked the initdb.log > file. It is zero bytes with no contents. > > After clicking OK, the installer rolls back, at which point I get > another dialog titled "Fatal Error" saying > > Installation ended prematurely because of an error. Very interesting error :-) That means the initdb process exited with an error code that certainly didn't come from initdb... Have you installed any non-standard security products, or done any lockdown from the standard level of the system? So that perhaps the postgres account doesn't have access to required DLL files? Also, when this happens, can you check the contents of 8.0.0-rc2\tmp\initdb.bat and see if the paths entered there are correct? Finally, do you get anything in the windows event logs when this happens? //Magnus ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] [pgsql-www] BUG #1356: pg_get_serial_sequence can not find a table that existing.
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane > Sent: 23 December 2004 15:30 > To: Kamp Kaibo Huang > Cc: [EMAIL PROTECTED]; pgsql-bugs@postgresql.org > Subject: Re: [pgsql-www] BUG #1356: pg_get_serial_sequence > can not find a table that existing. > > [ could we please get the bug form fixed to route bugs to the > right list? ] I did that first thing this morning - please let me know if anyone spots any further problems. Regards, Dave ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] BUG Postgresql 7.4.6 : usecreatedb flag
Stephane Raimbault <[EMAIL PROTECTED]> writes: > This bug (I suppose it's a bug) is very simple. > Fedora Core 3/postgresql-7.4.6-1.FC3.2 > su - postgres > createuser pguser > Answer yes and no so pguser can create db but can't create new user > ... > The flag in usecreatedb's column is false instead of true ! Works as expected for me. regards, tom lane ---(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] config option --with-pgport does not update postgresql.conf
Folks, Summary: --with-pgport option does not update postgresql.conf Severity: trivial Version: 8.0rc1 Platform: SuSE Linux 9.2, Celeron 1800mhz laptop Description: On a lark, I tried compiling RC1 using --with-pgport=5480, since I'm still using 7.4 on this machine as well. Once I finished INITDB, though, the generated postgresql.conf file still had: #port = 5432 This could be quite confusing to DBAs who were not aware that PG had been compiled with a different default. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
