Re: [BUGS] BUG #2776: unable to access created user directory

2006-11-25 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Nov 22, 2006 at 10:56:16AM +, Raghava wrote:
 
 The following bug has been logged online:
 
 Bug reference:  2776
 Logged by:  Raghava
 Email address:  [EMAIL PROTECTED]
 PostgreSQL version: 8.1.4
 Operating system:   RHEL
 Description:unable to access created user directory
 Details: 
 
 hi,
 
[...]
 su postgres
 bash-3.00$  psql  finaldb
 finaldb=# \i /home/schema.sql
  
 with this installtion of schema is working fine. But if i place the
 schema.sql in created user directory
 
 i.e useradd raghav
 directory raghav get's created under home floder. If i place schema.sql
 /home/raghav folder and execute the following commands
 
 su postgres
 bash-3.00$  psql  finaldb
 finaldb=# \i /home/raghav/schema.sql
 
 with the iam getting directory cannot be access.

This is supposed to work like that. It has nothing to do with
Postgresql, but with your Unix installation. It seems that by default on
your box one user is not allowed to read another user's home folder
(btw. we Unixers call that directory). This makes some sense.

This iam able to resolve
 by executing the command chmod -R 777 /home/raghav.

Wow. So anyone could remove all files in /home/raghav now. Do you want
that?

 But i have to handle this kind of issue through installtion script. Can u
 please suggest where are we are missing the configuration for postgres?

An installation script shold run as user postgres. The schema should be
part of the installation script and be readable by postgres.

If you have more questions we can continue off-list

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFZ9rSBcgs9XrR2kYRAp4dAJ9goEqmx8f7wXWZ3JEPzVCAV9VWHACfV+GC
XQylmdsHc0+no0Wi2DoOGJs=
=Afea
-END PGP SIGNATURE-


---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


[BUGS] BUG #2780: could not fsync segment 0

2006-11-25 Thread Thomas H.

The following bug has been logged online:

Bug reference:  2780
Logged by:  Thomas H.
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.2rc1
Operating system:   windows 2003 standard
Description:could not fsync segment 0
Details: 

still seeing lots of these errors on rc1 when doing bulk data load:

2006-11-26 04:34:30 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176087: Permission denied
2006-11-26 04:34:30 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied

2006-11-26 04:36:41 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176107: Permission denied
2006-11-26 04:36:41 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied

2006-11-26 04:38:47 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176119: Permission denied
2006-11-26 04:38:47 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied

2006-11-26 04:43:43 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176158: Permission denied
2006-11-26 04:43:43 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied

2006-11-26 04:59:39 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:39 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:40 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:40 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:41 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:41 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:42 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:42 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:43 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:43 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:44 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:44 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:45 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:45 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:46 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:46 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:47 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied
2006-11-26 04:59:47 [2124] ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-26 04:59:48 [2124] LOG:  could not fsync segment 0 of relation
1663/16692/2176296: Permission denied


all other problems i've been seeing in the earlier builds seem to be fixed.
thanks for the great work!

- thomas

---(end of broadcast)---
TIP 6: explain analyze is your friend