tablespaces

--_2cddd4fe-1f86-4521-86ee-950b8978cc25_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Can tablespaces be defined in the postgresql.conf file? In order to encryp=
t or databases we need a .decru file in $pg_data=2C this causes the tablesp=
ace command to fail. Initdb fails to=2C but we can work around it.

=20

Has anyone noticed that doing a PITR during DST (March-November) has the ef=
fect of being one ahead. Now I just adjust the requested time an hour ear=
lier=2C but is there a better way?

=20

~DjK
8.4.4
=20
____________________________________________________________ _____
The New Busy is not the too busy. Combine all your e-mail accounts with Hot=
mail.
http://www.windowslive.com/campaign/thenewbusy?tile=3Dmultia ccount&ocid=3DP=
ID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4=

--_2cddd4fe-1f86-4521-86ee-950b8978cc25_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable






Can tablespaces be defined in the postgresql.conf file? =3B In order to=
encrypt or databases we need a .decru file in $pg_data=2C this causes the =
tablespace command to fail. =3B Initdb fails to=2C but we can work arou=
nd it.

 =3B

Has anyone noticed that doing a PITR during DST (March-November) has the ef=
fect of being one ahead. =3B =3B Now I just adjust the requested ti=
me an hour earlier=2C but is there a better way?

 =3B

~DjK
8.4.4

Re: tablespaces

dx k9 wrote:

> Has anyone noticed that doing a PITR during DST (March-November)
> has the effect of being one ahead. Now I just adjust the
> requested time an hour earlier, but is there a better way?

I haven't noticed any odd behavior with PITR around Daylight Saving
Time boundaries. Could you describe exactly how you have it set up
and what you're seeing?

-Kevin

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Re: tablespaces

--_0f1c0175-70e6-4a85-9d26-939b9e7287f3_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


TIME ZONE is set to unknow in the conf file. The server syncs with NTP=2C=
has the correct time=2C but there is no TMZ env variable set. I set the =
recovery.conf to an hour before I want it and the logs show the time I want=
ed during DST. For example if I want a PITR of 9:55 AM=2C I put in 8:55 AM=
on the recovery.conf file=2C then the logs show a restore time of 9:55 AM =
was requested=2C and that's what gets processed. The non-DST part of the =
year=2C PITR works as expected and no adjustment is necessary.
=20
> Date: Thu=2C 15 Jul 2010 14:34:11 -0500
> From: Kevin.Grittner@wicourts.gov
> To: bitsandbytes88@hotmail.com=3B pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] tablespaces
>=20
> dx k9 wrote:
>=20
> > Has anyone noticed that doing a PITR during DST (March-November)
> > has the effect of being one ahead. Now I just adjust the
> > requested time an hour earlier=2C but is there a better way?
>=20
> I haven't noticed any odd behavior with PITR around Daylight Saving
> Time boundaries. Could you describe exactly how you have it set up
> and what you're seeing?
>=20
> -Kevin
=20
____________________________________________________________ _____
The New Busy is not the too busy. Combine all your e-mail accounts with Hot=
mail.
http://www.windowslive.com/campaign/thenewbusy?tile=3Dmultia ccount&ocid=3DP=
ID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4=

--_0f1c0175-70e6-4a85-9d26-939b9e7287f3_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable






TIME ZONE is set =3Bto unknow in the conf file. =3B =3B The ser=
ver =3Bsyncs with NTP=2C has the correct time=2C but there is no TMZ en=
v variable set. =3B =3B I set the recovery.conf to an hour before I=
want it and =3Bthe logs show the time I wanted during DST. =3B For=
example if I want =3Ba PITR of =3B9:55 AM=2C I =3Bput in 8:55 =
AM on the recovery.conf file=2C then the logs show a restore time of 9:55 A=
M was requested=2C and that's what gets processed. =3B =3B The non-=
DST part of =3Bthe year=2C PITR works as =3Bexpected and no adjustm=
ent is =3Bnecessary.
 =3B
>=3B Date: Thu=2C 15 Jul 2010 14:=
34:11 -0500
>=3B From: Kevin.Grittner@wicourts.gov
>=3B To: bitsa=
ndbytes88@hotmail.com=3B pgsql-admin@postgresql.org
>=3B Subject: Re: =
[ADMIN] tablespaces
>=3B
>=3B dx k9 <=3Bbitsandbytes88@hotmail=
..com>=3B wrote:
>=3B
>=3B >=3B Has anyone noticed that doing=
a PITR during DST (March-November)
>=3B >=3B has the effect of bein=
g one ahead. Now I just adjust the
>=3B >=3B requested time an hour =
earlier=2C but is there a better way?
>=3B
>=3B I haven't notice=
d any odd behavior with PITR around Daylight Saving
>=3B Time boundari=
es. Could you describe exactly how you have it set up
>=3B and what yo=
u're seeing?
>=3B
>=3B -Kevin