Re: [ADMIN] Time Zone in Postgres
Hi Tom, We have different databases with different versions. I checked the database with *version 8.2.4* by running the below query echo select timestamp with time zone \'epoch\' + 1206970200 \* INTERVAL \'1 second\'\; | psql template1 ?column? --- 2008-03-31 23:00:00+09:30 (1 row) This shows the wrong date. The actual result should be *2008-04-01 00:00:00+10:30 * Thanks and Regards, On Fri, Mar 7, 2008 at 4:53 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > Vishal Arora <[EMAIL PROTECTED]> writes: > > Hi, I've been working on a timezone issue. I am in Adelaide Australia > > and the daylight savings time this year has been changed. I am trying > > to figure out the file which is required to be changed. > > The easiest and best solution would be to update to a newer PG release > than 8.0.9 --- installing 8.0.15 over it would be painless and would fix > a number of problems besides this one, including some rather nasty > data-loss risks. > > If you really can't be bothered with that, you can probably use your > operating system's copy of the timezone data files (try under > /usr/share/zoneinfo for starters). > >regards, tom lane >
[ADMIN] Getting an error in connection refused
Hi, I'm trying to connect to databasewhich has been already created. But when I use following command psql -Utest1 -hlocalhost -p5432 -W testone I'm getting the following error psql: could not connect to server: Connection refused Is the server running on host "localhost" and accepting TCP/IP connections on port 5432? Can anybody please tell me how to solve this problem Thanks and Regards Shilpa ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[ADMIN] pg_ctl reload query
Hi All, Wanted to know what does pg_ctl do in the background when we run *pg_ctl -D datadir reload * After modifying the entries in pg_hba.conf file we ran the reload command. Generally, it just reloads the files and everything works fine. But strangely, last time when we ran the reload command and tried to access *psql dbname, * It gives a message *"database shutting down" * As far as i know, this msg appears only when a restart command is given. Please let me know if my understanding is right and what could have gone wrong for the db to shutdown. Thanks and Regards, Shilpa * * ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] pg_ctl reload query
Thanks for the reply. I am sure i didn't issue the restart command. i only did the reload. I'll find out from my other team mates if they issued any restart command by mistake. Thanks again. Regards, Shilpa Andrew Sullivan wrote: On Thu, Feb 21, 2008 at 04:01:00PM +1030, Shilpa Sudhakar wrote: Hi All, Wanted to know what does pg_ctl do in the background when we run *pg_ctl -D datadir reload * It sends a SIGHUP to the back end. command. Generally, it just reloads the files and everything works fine. But strangely, last time when we ran the reload command and tried to access *psql dbname, * It gives a message *"database shutting down" * Are you sure you didn't issue "restart" instead? It's an easy enough mistake to make. A ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq ---(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
[ADMIN] WAL archiving
Hi All, I am new to postgres and have been slowly learning the concepts. Regarding WAL archiving, we first take a base backup and then save all the wal logs for PITR. Both the base backup and wal logs are stored in another disk. Since the wal logs keep increasing, do we take the base backup every now and then so that we can delete the old log files? How often do we take a base filesystem backup keeping in mind that our systems are 24 x 7. Any suggestions are appreciated. Thanks and Regards, Shilpa ---(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
Re: [ADMIN] WAL archiving
Shilpa Sudhakar wrote: Hi Vishal, Below is the setup in the postgresql.conf file fsync = true# turns forced synchronization on or off wal_sync_method = fsync # the default varies across platforms: #wal_buffers = 8# min 4, 8KB each #commit_delay = 0 # range 0-10, in microseconds #commit_siblings = 5# range 1-1000 # - Checkpoints - checkpoint_segments = 3 # in logfile segments, min 1, 16MB each checkpoint_timeout = 300# range 30-3600, in seconds checkpoint_warning = 30 # 0 is off, in seconds # - Archiving - archive_command = 'cp -i %p /usr/local/var/pgsql/data/wal_log/%f' # command to use to archive a logfile segment Since this is the test system i've put the wal_log folder in the data folder itself. But, later on i'll be moving this to a different disk. We have thousands and thousands of records that get inserted and updated so the wal logs would be increasing in a large rate. I was thinking if i want to delete the wal logs after a period of time, do i take a base backup again and then delete those old files? Thanks and Regards, Shilpa Vishal Arora wrote: Hi Shilpa, You need not take base backup again and again. You have WAL Archiveing in place, that is enough to restore the database. BTW, what archiving command are you using for WAL Archiving in you postgresql.conf. - Vishal > Date: Fri, 22 Feb 2008 09:53:25 +1030 > From: [EMAIL PROTECTED] > To: pgsql-admin@postgresql.org > Subject: [ADMIN] WAL archiving > > Hi All, > > I am new to postgres and have been slowly learning the concepts. > > Regarding WAL archiving, we first take a base backup and then save all > the wal logs for PITR. > > Both the base backup and wal logs are stored in another disk. > > Since the wal logs keep increasing, do we take the base backup every now > and then so that we can delete the old log files? > How often do we take a base filesystem backup keeping in mind that our > systems are 24 x 7. > > Any suggestions are appreciated. > > Thanks and Regards, > Shilpa > > > ---(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 It's about getting married. Click here! Try it! <http://ss1.richmedia.in/recurl.asp?pid=201> ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [ADMIN] WAL archiving
Thanks loads Dawid, I'll test the process on the TEST box and note down the time it takes. Dawid Kuroczko wrote: On Fri, Feb 22, 2008 at 12:23 AM, Shilpa Sudhakar <[EMAIL PROTECTED]> wrote: Since the wal logs keep increasing, do we take the base backup every now and then so that we can delete the old log files? How often do we take a base filesystem backup keeping in mind that our systems are 24 x 7. Depends on your workload and needs. Say, if you have a policy on having ability to "go back in time" for at least 30 days, then you must keep last base backup that was done before 30 days and all the log files since then. But your primary concern should be probably recovery time after failure (your whole machine just fried ;)). What you need to do is restore last backup and reply all archival WAL logs since then. And assume worst possible situation (the machine fried just before full backup), for a weekly backups it means 7 days worth of WAL-log reply. Now, if your database is DML-heavy recovery won't be very fast, so you might want to take base backups more frequently. Or better -- set up a standby server which will constantly reply the backups. Regards, Dawid Kuroczko PS: And before setting a policy, do try test recovery and note down how much time it took. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] WAL archiving
Thanks a lot Vishal for the info. I have one more query postgres automatically cleans the WAL files present in the pg_xlog directoryright? So instead of me creating a separate folder as i've done in my current settings (wal_log), should i need to change the archive_command to point to pg_xlog directly. In this way i can avoid a separate process of deleting old files. Please let me know if my understanding is right. Thanks and Regards, Shilpa Vishal Arora wrote: > Date: Mon, 25 Feb 2008 09:53:35 +1030 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [ADMIN] WAL archiving > > Hi Vishal, > > Below is the setup in the postgresql.conf file > > fsync = true # turns forced synchronization on or off > wal_sync_method = fsync # the default varies across platforms: > #wal_buffers = 8 # min 4, 8KB each > #commit_delay = 0 # range 0-10, in microseconds > #commit_siblings = 5 # range 1-1000 > > # - Checkpoints - > > checkpoint_segments = 3 # in logfile segments, min 1, 16MB each > checkpoint_timeout = 300 # range 30-3600, in seconds > checkpoint_warning = 30 # 0 is off, in seconds > > # - Archiving - > > archive_command = 'cp -i %p /usr/local/var/pgsql/data/wal_log/%f' > # command to use to archive a logfile segment > > Since this is the test system i've put the wal_log folder in the data > folder itself. But, later on i'll be moving this to a different disk. > > We have thousands and thousands of records that get inserted and updated > so the wal logs would be increasing in a large rate. I was thinking if i > want to delete the wal logs after a period of time, do i take a base > backup again and then delete those old files? Not required actually. Once you have base backup and Archived WAL in place, you need not take a base backup again. In case of a crash you just have to restore from the base backup and the server would start in restore mode. In restore.conf file you have to specify the restore_command - which would point towards the archived WAL files. Yes Once the WAL has been archived you can delete the old WAL files, which is also done by the postgres itself. It replaces the old(not required) WAL files with the new one. > Thanks and Regards, > Shilpa > > > Vishal Arora wrote: > > > > Hi Shilpa, > > > > You need not take base backup again and again. You have WAL Archiveing > > in place, that is enough to restore the database. BTW, what archiving > > command are you using for WAL Archiving in you postgresql.conf. > > > > - Vishal > > > > > > > > > Date: Fri, 22 Feb 2008 09:53:25 +1030 > > > From: [EMAIL PROTECTED] > > > To: pgsql-admin@postgresql.org > > > Subject: [ADMIN] WAL archiving > > > > > > Hi All, > > > > > > I am new to postgres and have been slowly learning the concepts. > > > > > > Regarding WAL archiving, we first take a base backup and then save all > > > the wal logs for PITR. > > > > > > Both the base backup and wal logs are stored in another disk. > > > > > > Since the wal logs keep increasing, do we take the base backup every > > now > > > and then so that we can delete the old log files? > > > How often do we take a base filesystem backup keeping in mind that our > > > systems are 24 x 7. > > > > > > Any suggestions are appreciated. > > > > > > Thanks and Regards, > > > Shilpa > > > > > > > > > ---(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 > > > > > > > > It's about getting married. Click here! Try it! > > <http://ss1.richmedia.in/recurl.asp?pid=201> > Post free auto ads on Yello Classifieds now! Try it now! <http://ss1.richmedia.in/recurl.asp?pid=255> ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] WAL archiving
Thanks for the link Vishal Regards, Shilpa Vishal Arora wrote: You can have a warm standby system in place. Pls check this link - http://archives.postgresql.org/sydpug/2006-10/msg1.php > Date: Mon, 25 Feb 2008 09:54:34 +1030 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] WAL archiving > > Shilpa Sudhakar wrote: > > Hi Vishal, > > > > Below is the setup in the postgresql.conf file > > > > fsync = true # turns forced synchronization on or off > > wal_sync_method = fsync # the default varies across platforms: > > #wal_buffers = 8 # min 4, 8KB each > > #commit_delay = 0 # range 0-10, in microseconds > > #commit_siblings = 5 # range 1-1000 > > > > # - Checkpoints - > > > > checkpoint_segments = 3 # in logfile segments, min 1, 16MB each > > checkpoint_timeout = 300 # range 30-3600, in seconds > > checkpoint_warning = 30 # 0 is off, in seconds > > > > # - Archiving - > > > > archive_command = 'cp -i %p /usr/local/var/pgsql/data/wal_log/%f' > > # command to use to archive a logfile segment > > > > Since this is the test system i've put the wal_log folder in the data > > folder itself. But, later on i'll be moving this to a different disk. > > > > We have thousands and thousands of records that get inserted and > > updated so the wal logs would be increasing in a large rate. I was > > thinking if i want to delete the wal logs after a period of time, do i > > take a base backup again and then delete those old files? > > > > Thanks and Regards, > > Shilpa > > > > > > Vishal Arora wrote: > >> > >> Hi Shilpa, > >> > >> You need not take base backup again and again. You have WAL > >> Archiveing in place, that is enough to restore the database. BTW, > >> what archiving command are you using for WAL Archiving in you > >> postgresql.conf. > >> > >> - Vishal > >> > >> > >> > >> > Date: Fri, 22 Feb 2008 09:53:25 +1030 > >> > From: [EMAIL PROTECTED] > >> > To: pgsql-admin@postgresql.org > >> > Subject: [ADMIN] WAL archiving > >> > > >> > Hi All, > >> > > >> > I am new to postgres and have been slowly learning the concepts. > >> > > >> > Regarding WAL archiving, we first take a base backup and then save all > >> > the wal logs for PITR. > >> > > >> > Both the base backup and wal logs are stored in another disk. > >> > > >> > Since the wal logs keep increasing, do we take the base backup > >> every now > >> > and then so that we can delete the old log files? > >> > How often do we take a base filesystem backup keeping in mind that our > >> > systems are 24 x 7. > >> > > >> > Any suggestions are appreciated. > >> > > >> > Thanks and Regards, > >> > Shilpa > >> > > >> > > >> > ---(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 > >> > >> > >> > >> It's about getting married. Click here! Try it! > >> <http://ss1.richmedia.in/recurl.asp?pid=201> > > > > > > > ---(end of broadcast)--- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate Post free auto ads on Yello Classifieds now! Try it now! <http://ss1.richmedia.in/recurl.asp?pid=255> ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] WAL archiving
Thanks Vishal. I got it now. Will test the archiving process. Vishal Arora wrote: > Date: Mon, 25 Feb 2008 15:30:46 +1030 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] WAL archiving > > Thanks a lot Vishal for the info. > > I have one more query postgres automatically cleans the WAL files > present in the pg_xlog directoryright? YES! it actually recycles the files which are of no further intrest. So instead of me creating a separate folder as i've done in my current > settings (wal_log), should i need to change the archive_command to point > to pg_xlog directly. NO! In this case it would try to overwrite the existing WAL files. pg_xlog already contains the WAL files .. whats the point archiving the files at the same place. Refer to Chapter 23.3.1 (8.2) of the Manual - "The archive command should generally be designed to refuse to overwrite any pre-existing archive file. This is an important safety feature to preserve the integrity of your archive in case of administrator error (such as sending the output of two different servers to the same archive directory). It is advisable to test your proposed archive command to ensure that it indeed does not overwrite an existing file, and that it returns nonzero status in this case. " > In this way i can avoid a separate process of deleting old files. > > Please let me know if my understanding is right. > > Thanks and Regards, > Shilpa > > > > Vishal Arora wrote: > > > > > > > > > > > > > > > > > Date: Mon, 25 Feb 2008 09:53:35 +1030 > > > From: [EMAIL PROTECTED] > > > To: [EMAIL PROTECTED] > > > Subject: Re: [ADMIN] WAL archiving > > > > > > Hi Vishal, > > > > > > Below is the setup in the postgresql.conf file > > > > > > fsync = true # turns forced synchronization on or off > > > wal_sync_method = fsync # the default varies across platforms: > > > #wal_buffers = 8 # min 4, 8KB each > > > #commit_delay = 0 # range 0-10, in microseconds > > > #commit_siblings = 5 # range 1-1000 > > > > > > # - Checkpoints - > > > > > > checkpoint_segments = 3 # in logfile segments, min 1, 16MB each > > > checkpoint_timeout = 300 # range 30-3600, in seconds > > > checkpoint_warning = 30 # 0 is off, in seconds > > > > > > # - Archiving - > > > > > > archive_command = 'cp -i %p /usr/local/var/pgsql/data/wal_log/%f' > > > # command to use to archive a logfile segment > > > > > > Since this is the test system i've put the wal_log folder in the data > > > folder itself. But, later on i'll be moving this to a different disk. > > > > > > We have thousands and thousands of records that get inserted and > > updated > > > so the wal logs would be increasing in a large rate. I was thinking > > if i > > > want to delete the wal logs after a period of time, do i take a base > > > backup again and then delete those old files? > > > > Not required actually. Once you have base backup and Archived WAL in > > place, you need not take a base backup again. In case of a crash you > > just have to restore from the base backup and the server would start > > in restore mode. In restore.conf file you have to specify the > > restore_command - which would point towards the archived WAL files. > > Yes Once the WAL has been archived you can delete the old WAL files, > > which is also done by the postgres itself. It replaces the old(not > > required) WAL files with the new one. > > > > > Thanks and Regards, > > > Shilpa > > > > > > > > > Vishal Arora wrote: > > > > > > > > Hi Shilpa, > > > > > > > > You need not take base backup again and again. You have WAL > > Archiveing > > > > in place, that is enough to restore the database. BTW, what archiving > > > > command are you using for WAL Archiving in you postgresql.conf. > > > > > > > > - Vishal > > > > > > > > > > > > > > > > > > > Date: Fri, 22 Feb 2008 09:53:25 +1030 > > > > > From: [EMAIL PROTECTED] > > > > > To: pgsql-admin@postgresql.org > &g
Re: [ADMIN] Time Zone in Postgres
Hi Tom, We have different databases with different versions. I checked the database with *version 8.2.4* by running the below query echo select timestamp with time zone \'epoch\' + 1206970200 \* INTERVAL \'1 second\'\; | psql template1 ?column? --- 2008-03-31 23:00:00+09:30 (1 row) This shows the wrong date. The actual result should be *2008-04-01 00:00:00+10:30 * Thanks and Regards, Tom Lane wrote: Vishal Arora <[EMAIL PROTECTED]> writes: Hi, I've been working on a timezone issue. I am in Adelaide Australia and the daylight savings time this year has been changed. I am trying to figure out the file which is required to be changed. The easiest and best solution would be to update to a newer PG release than 8.0.9 --- installing 8.0.15 over it would be painless and would fix a number of problems besides this one, including some rather nasty data-loss risks. If you really can't be bothered with that, you can probably use your operating system's copy of the timezone data files (try under /usr/share/zoneinfo for starters). regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-admin -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-admin
Re: [ADMIN] Time Zone in Postgres
Hi Cat, As per my previous mail, i've done few checks on the postgres timezone files but not sure if am looking at the right file. I'll paste the details again below . 1) Checked the *postgresql.conf file* and the *timezone *parameter is set as "*unknown*". 2) */local/pkgsrc/databases/postgresql80-pgcrypto/work/postgresql-8.0.9/src/timezone/data $ grep 2007 australasia* RuleAS 2007max - Mar lastSun 2:00s 0 - RuleAT 2007max - Mar lastSun 2:00s 0 - RuleAV 2007max - Mar lastSun 2:00s 0 - RuleAN 2007max - Mar lastSun 2:00s 0 - RuleLH 2007max - Mar lastSun 2:000 - */local/pkgsrc/databases/postgresql80-pgcrypto/work/postgresql-8.0.9/src/timezone/data $ grep 2008 australasia* No results From 2008, the DST ends on first Sunday of April and not on the last Sun of March. Thanks [EMAIL PROTECTED] wrote: On Fri, Mar 07, 2008 at 09:26:51AM +1030, Shilpa Sudhakar wrote: Hi Tom, We have different databases with different versions. I checked the database with *version 8.2.4* by running the below query echo select timestamp with time zone \'epoch\' + 1206970200 \* INTERVAL \'1 second\'\; | psql template1 ?column? --- 2008-03-31 23:00:00+09:30 (1 row) This shows the wrong date. The actual result should be *2008-04-01 00:00:00+10:30 * I believe postgres comes with its own timezone info. Check if the stuff it has has the right timezone information. Personally I get it to use the system timezone definitions so that I can keep things upto-date easier. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Time Zone in Postgres
Hi Alvaro, Thanks for the info. I assume Postgresql should have already known about the DST changes in Australia. I'll check the mailing list from the link you sent to see if there's anything regarding this. Thanks and Regards, Alvaro Herrera wrote: Shilpa Sudhakar wrote: From 2008, the DST ends on first Sunday of April and not on the last Sun of March. Please report this issue to the guys maintaining the TZ database upstream: http://news.gmane.org/gmane.comp.time.tz Because my country is having a TZ DST change this Saturday, a new release of tzdata is coming out tomorrow or the day after, so if this issue wasn't already reported you'll probably miss it. Still, it would be very good to be quick about it so your changes are present in the next release due shortly thereafter. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Time Zone in Postgres
Hi Tom, If DST changes are done in version 8.2.5 and up, is there any way to recompile the timezone files in our existing versions without upgrading. Thanks Tom Lane wrote: Alvaro Herrera <[EMAIL PROTECTED]> writes: Shilpa Sudhakar wrote: From 2008, the DST ends on first Sunday of April and not on the last Sun of March. Please report this issue to the guys maintaining the TZ database upstream: You sure they don't know about it already? # southeast Australia # # From Paul Eggert (2007-07-23): # Starting autumn 2008 Victoria, NSW, South Australia, Tasmania and the ACT # end DST the first Sunday in April and start DST the first Sunday in October. # http://www.theage.com.au/news/national/daylight-savings-to-span-six-months/2007/06/27/1182623966703.html This is in our releases 8.2.5 and up. If the OP wants to live under a government that feels free to whack DST laws around on a couple months' notice, he's got to be prepared to keep up with software updates. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Time Zone in Postgres
Hi Tom, I live in Adelaide Australia. I checked in 3 servers and all of them have "Australia/South" when i ran "show timezone" For the new timezone files, do i need to apply a timezone patch? Thanks Tom Lane wrote: Shilpa Sudhakar <[EMAIL PROTECTED]> writes: 1) Checked the *postgresql.conf file* and the *timezone *parameter is set as "*unknown*". What does SHOW TIMEZONE report? Given the above, Postgres will try to deduce what zone your operating system is using, but that doesn't always work perfectly (especially if PG's timezone database isn't quite in sync with the system's). If it guessed wrong, you might have to explicitly set the appropriate zone in postgresql.conf. You weren't very clear about where you live, so I don't know which of the numerous Australia/wherever zones you should use... */local/pkgsrc/databases/postgresql80-pgcrypto/work/postgresql-8.0.9/src/timezone/data $ grep 2008 australasia* No results Well, no. 8.0.9 was released on 2006-10-16, many months before that change in DST laws was passed. You need a newer set of zoneinfo files. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Time Zone in Postgres
Hi Tom, Thanks. I'll look into upgrading the database. Since we have a huge bunch of databases i was thinking of an alternative for now. As i said, we have version 8.2.4 databases and if i need to just update the timezone files for this database do i copy the zoneinfo files from the OS zonefile or from the newer version of Postgres zonefiles. Thanks Tom Lane wrote: Alvaro Herrera <[EMAIL PROTECTED]> writes: Shilpa Sudhakar wrote: If DST changes are done in version 8.2.5 and up, is there any way to recompile the timezone files in our existing versions without upgrading. FWIW this change is also in 8.1.11. ... and 8.0.14 ... Anyway, yes, you could get the newer zoneinfo source files and run them through zic, but it's hard to see why that would be a smarter thing to do than a database update. There are known data-loss bugs in the minor version you're running, and you ought to be a lot more worried about those than about whether Postgres is a week off about the next DST transition. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Time Zone in Postgres
I copied the system zonefiles into the postgres database and it works fine now. This is anyway a temporary solution until we upgrade all our systems. Thanks to all for your suggestions and help. Tom Lane wrote: Shilpa Sudhakar <[EMAIL PROTECTED]> writes: As i said, we have version 8.2.4 databases and if i need to just update the timezone files for this database do i copy the zoneinfo files from the OS zonefile or from the newer version of Postgres zonefiles. If your platform uses the standard zoneinfo format (and if the file trees look similar, it probably does) then you could just copy the system's zoneinfo files into the Postgres directories, assuming you've gotten updated zoneinfo files for the system. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
[ADMIN] ident authentication
Hi, I am trying to test different kinds of authentication in postgres. I'm to find a efficient way to link the OS user with the postgres user. This is to help for auditing purpose. This is similar to the query raised by another postgres user. As suggested by Tom to use ident, i tried setting up ident but it isn't working. In the hba.conf file, i add the below entry local all all ident sameuser The user logged in at OS level is "abc". I created a user "abc" in postgres but when i do "psql -U abc -d dbname", i get the below error: FATAL: Ident authentication failed for user "abc" Should i put an entry in pg_ident.conf file? Is using ident still the right way to go? Is LDAP a better option because when we login to the server, we login with our LDAP username and password. Thanks and Regards, Shilpa -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
