Got it, I didn't see the toast word in the command. Thanks !
On Thu, Jan 17, 2019, 10:17 PM Alvaro Herrera On 2019-Jan-17, Mariel Cherkassky wrote:
>
> > But you said that the threshold that is chosen for the toasted table is
> > identical to the originals table threshold right ?
>
> You can conf
On 2019-Jan-17, Mariel Cherkassky wrote:
> But you said that the threshold that is chosen for the toasted table is
> identical to the originals table threshold right ?
You can configure them identical, or different. Up to you.
> Is that a normal behavior that the original table has 1000recrods
But you said that the threshold that is chosen for the toasted table is
identical to the originals table threshold right ? Is that a normal
behavior that the original table has 1000recrods but the toasted has more
than 10m? How can I set a different threshold for the toasted table ? As it
seems rig
On 2019-Jan-17, Mariel Cherkassky wrote:
> I did it for the original table. But I see in the logs that the autovacuun
> on the toasted table isn't synced with the autovacuun of the original
> table. Therefore I thought that it worth to set it also for the toasted
> table. Can you explain why in th
I did it for the original table. But I see in the logs that the autovacuun
on the toasted table isn't synced with the autovacuun of the original
table. Therefore I thought that it worth to set it also for the toasted
table. Can you explain why in the logs I see more vacuums of the original
table th
On 2019-Jan-17, Mariel Cherkassky wrote:
> I tried to set the same threshold for the toasted table but got an error
> that it is a catalog table and therefore permission is denied.
> 2019-01-17 12:04:15 EST db116109 ERROR: permission denied:
> "pg_toast_13388392" is a system catalog
> 2019-01-17
On Thu, Jan 17, 2019 at 07:28:52PM +0200, Mariel Cherkassky wrote:
...
> Now, I realized from the autovacuum
> logging, that when autovacuum runs on the original table (A) it doesn't
> necessary run on the toasted table and this is very weird.
...
> Any idea why the autovacuum doesnt vacuum both ta
Hey,
I have a table with 3 columns and one of those columns is bytea type
A(int,int,bytea).
Every row that I insert is pretty big and thats why postgresql decided to
save that column in a toasted table(pg_toasted_Aid). I had a lot of bloat
issues with that table so I set the vacuum_threshold of the
Daulat Ram wrote:
> We have enabled the monitoring to monitor the vacuuming of tables via
> check_postgres_last_vacuum plugin but we are getting the below warning
> message.
>
> Notification Type: PROBLEM
> Service: PostgreSQL last vacuum ()
> Host Alias: vmshowcasedb2.vpc.prod.scl1.us.tribalfu
