Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://bolha.one/users/cadusilva/statuses/113538891069548891">Cadu Silva :verified: (cadusilva@bolha.one)'s status on Monday, 25-Nov-2024 01:33:17 JST</a><a href="https://bolha.one/@cadusilva" title="cadusilva@bolha.one"><img src="https://gnusocial.jp/avatar/43507-48-20241111170358.webp" width="48" height="48" alt="Cadu Silva :verified:" style="position: absolute; left: 0; top: 0;">Cadu Silva :verified:</a><div><a href="https://gnusocial.jp/notice/7937855" rel="in-reply-to">in reply to</a></div></section><article><p>Se por acaso algum de vocês se deparar com um erro desses no PostgreSQL, aqui tem a solução:</p><p>🔧 <a href="https://blog.dob.sk/2012/05/19/fixing-pg_dump-invalid-memory-alloc-request-size/" rel="nofollow noreferrer">https://blog.dob.sk/2012/05/19/fixing-pg_dump-invalid-memory-alloc-request-size/</a> (<a href="https://archive.is/1heQZ" rel="nofollow noreferrer">https://archive.is/1heQZ</a>)</p><p>Na corrupção anterior, o erro reclamava de "compressed data is corrupt". O que me ajudou foi essa resposta:</p><p>🔧 <a href="https://dba.stackexchange.com/a/127958" rel="nofollow noreferrer">https://dba.stackexchange.com/a/127958</a></p><p><a href="https://a.gup.pe/u/fediadminbr">@fediadminbr</a> </p><p><a href="https://bolha.one/tags/MastoAdmin" rel="tag">#MastoAdmin</a> <a href="https://bolha.one/tags/FediAdminBR" rel="tag">#FediAdminBR</a> <a href="https://bolha.one/tags/PostgreSQL" rel="tag">#PostgreSQL</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4062113#notice-7937996">In conversation</a><time datetime="2024-11-25T01:33:17+09:00" title="Monday, 25-Nov-2024 01:33:17 JST">about 4 days ago</time> <span>from <span><a href="https://bolha.one/@cadusilva/113538891069548891" rel="external" title="Sent from bolha.one via ActivityPub">bolha.one</a></span></span><a href="https://bolha.one/@cadusilva/113538891069548891">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://blog.dob.sk/2012/05/19/fixing-pg_dump-invalid-memory-alloc-request-size/">Fixing pg_dump invalid memory alloc request size</a></h5><div></div></header><div></div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: archive.is</div><h5><a href="https://archive.is/1heQZ">Fixing pg_dump invalid memory alloc request size – DOB blog</a></h5><div></div></header><div>archived 24 Nov 2024 16:21:51 UTC</div><footer></footer></article></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/3559062">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Cadu Silva :verified: (cadusilva@bolha.one)'s status on Monday, 25-Nov-2024 01:33:17 JST Cadu Silva :verified:
in reply to
Se por acaso algum de vocês se deparar com um erro desses no PostgreSQL, aqui tem a solução:
🔧 https://blog.dob.sk/2012/05/19/fixing-pg_dump-invalid-memory-alloc-request-size/ (https://archive.is/1heQZ)
Na corrupção anterior, o erro reclamava de "compressed data is corrupt". O que me ajudou foi essa resposta:
🔧 https://dba.stackexchange.com/a/127958
@fediadminbr
#MastoAdmin #FediAdminBR #PostgreSQL
In conversationabout 4 days ago from bolha.onepermalink
Attachments
1. No result found on File_thumbnail lookup.
  Fixing pg_dump invalid memory alloc request size
2. Domain not in remote thumbnail source whitelist: archive.is
  Fixing pg_dump invalid memory alloc request size – DOB blog
  archived 24 Nov 2024 16:21:51 UTC
3. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice