| From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
|---|---|
| To: | ZEUGSWETTER Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, "'kar(at)webline(dot)dk'" <kar(at)webline(dot)dk> |
| Subject: | Re: [HACKERS] 6.6 items |
| Date: | 1999-06-08 07:44:54 |
| Message-ID: | 375CC9F6.3D97B7E0@krs.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
ZEUGSWETTER Andreas IZ5 wrote:
>
> > - Up time. This means hot backup and no locking of the database during
> > vacuum.
> >
> If Vadim made the change to make pg_dump dump in one transaction then
> PostgreSQL already has "hot backup" in 6.5. This will do a consistent
> snapshot of your database as it was when pg_dump began as long as you
> don't change the database layout during the dump.
This is done.
Vacuum doesn't lock entire database. But it acquires access
exclusive lock over table being vacuumed and so delay all
(even SELECT) concurrent query executions. Lock released
after table vacuumed.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Broytmann | 1999-06-08 08:02:13 | Re: [HACKERS] PostgreSQL History(Parody) |
| Previous Message | Dmitry Samersoff | 1999-06-08 07:42:24 | Re: [HACKERS] Priorities for 6.6 |