On Tue, Dec 5, 2017 at 6:12 AM, Alvaro Herrera wrote:
> sql2pg wrote:
>> how about uncommitted(open transactions) . if a segment has 1 committed and
>> 2 uncommitted transactions then will it keep the segment instead deleting it
>> after checkpoint , since it has 2 uncommitted transactions
>
> Th
sql2pg wrote:
> how about uncommitted(open transactions) . if a segment has 1 committed and
> 2 uncommitted transactions then will it keep the segment instead deleting it
> after checkpoint , since it has 2 uncommitted transactions
There is no connection between transaction commit and checkpoint
how about uncommitted(open transactions) . if a segment has 1 committed and
2 uncommitted transactions then will it keep the segment instead deleting it
after checkpoint , since it has 2 uncommitted transactions
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On Mon, Dec 4, 2017 at 8:50 AM, sql2pg wrote:
> Is Postgres removes the committed transaction after archive. LIke in SQL
> Server , which removes the committed transactions after taking Log backup.
>
If I understand correctly, yes - eventually. The docs explain the behavior
and the configurati
Is Postgres removes the committed transaction after archive. LIke in SQL
Server , which removes the committed transactions after taking Log backup.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html