| From: | "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com> |
|---|---|
| To: | thomas(at)chille(dot)de |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: initskript after db start; locks on transactions |
| Date: | 2005-08-05 17:49:10 |
| Message-ID: | 9F4A0406-00C7-47EA-99EC-2892AC45C755@sitening.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Aug 3, 2005, at 4:33 PM, Thomas Chille wrote:
> Hi!
>
> I have have two questions:
>
> 1.
> What is the best approach to trigger a service script wich will clean
> up something in the db after every db (re-)start? Has PG its own
> mechanism for such things or have i to use my /etc/init.d/postgresql
> script?
I don't think there's anything built in that will trigger a "service
script". I'm pretty sure you'll want to add to or supplement the
existing init script.
> 2.
> Sometime i read something about locks on transactions. Is this only an
> internal thing or can i set them by my own and if yes, for what? With
> the LOCK command i can only lock tables, or?
You can use any lock mode specified:
http://www.postgresql.org/docs/8.0/static/sql-lock.html
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Pundt | 2005-08-05 19:06:22 | Re: DNS vs /etc/hosts |
| Previous Message | Patrick Hatcher | 2005-08-05 16:55:55 | slow update query |