Rich Ford wrote:
When running alterdb -delete_oldest_ckp how does Ingres determine the oldest available checkpoint?It gets it from the checkpoint history recorded in the database
configuration file. That file lives in the default data area of the
database. It's called aaaaaaaa.cnf but it's a binary file that is hard
for a human user to interpret.
Fortunately you don't have to interpret it. The infodb utility dumps the
file contents, including the checkpoint history, in a readable format.
The history array can save about 99 checkpoints IIRC... If you
somehow manage to accumulate more checkpoints than that they become
invisible and can no longer be deleted using alterdb.
Roy
On Thursday, 2 December 2021 at 09:27:18 UTC-8, Roy Hann wrote:
Rich Ford wrote:
When running alterdb -delete_oldest_ckp how does Ingres determine the oldest available checkpoint?It gets it from the checkpoint history recorded in the database
configuration file. That file lives in the default data area of the
database. It's called aaaaaaaa.cnf but it's a binary file that is hard
for a human user to interpret.
Fortunately you don't have to interpret it. The infodb utility dumps the
file contents, including the checkpoint history, in a readable format.
The history array can save about 99 checkpoints IIRC... If you
somehow manage to accumulate more checkpoints than that they become
invisible and can no longer be deleted using alterdb.
Can this be modified to only store 1 checkpoint?
We currently are storing 2 but running low on disk space.
When running alterdb -delete_oldest_ckp how does Ingres determine the oldest available checkpoint?
Rich Ford wrote:
On Thursday, 2 December 2021 at 09:27:18 UTC-8, Roy Hann wrote:
Rich Ford wrote:
When running alterdb -delete_oldest_ckp how does Ingres determine the oldest available checkpoint?It gets it from the checkpoint history recorded in the database
configuration file. That file lives in the default data area of the
database. It's called aaaaaaaa.cnf but it's a binary file that is hard
for a human user to interpret.
Fortunately you don't have to interpret it. The infodb utility dumps the >> file contents, including the checkpoint history, in a readable format.
The history array can save about 99 checkpoints IIRC... If you
somehow manage to accumulate more checkpoints than that they become
invisible and can no longer be deleted using alterdb.
Can this be modified to only store 1 checkpoint?alterdb -keep=1 ...
We currently are storing 2 but running low on disk space.
Roy
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 344 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 81:23:35 |
| Calls: | 7,537 |
| Calls today: | 2 |
| Files: | 12,720 |
| Messages: | 5,645,116 |