I received a question about this error.
Just for the record, if someone encounter the same issue.
It has been fixed in ff9f111bce24
TL;DR : update your instance :)
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=ff9f111bce24
Fix WAL replay in presence of an incomplete record
Ph
On 1/9/23 11:23, Torsten Förtsch wrote:
On Mon, Jan 9, 2023 at 10:59 AM Adrien Nayrat
mailto:adrien.nay...@anayrat.info>> wrote:
* We can't perform PITR on a cluster without any activity since 13
* It seems creating restore point doesn't record a timestamp in wal.
I
Hello,
I bump this thread up, I hope to have more reaction :)
TL;DR:
* We can't perform PITR on a cluster without any activity since 13
* It seems creating restore point doesn't record a timestamp in wal.
Thanks
--
Adrien NAYRAT
Thanks
--
Adrien NAYRAT
On 5/6/21 7:37 AM, Kyotaro Horiguchi wrote:
At Sun, 2 May 2021 22:43:44 +0200, Adrien Nayrat
wrote in
I also dumped 000100AA00A1 on the secondary and it
contains all the records until AA/A1004018.
It is really weird, I don't understand how the secondary can miss the
l
U2xevmxQ%40mail.gmail.com
https://www.postgresql.org/message-id/flat/E73F4CFB-E322-461E-B1EC-82FAA808FEE6%40lifetrenz.com
https://www.postgresql.org/message-id/15398-b4896eebf0bed218%40postgresql.org
https://www.postgresql.org/message-id/flat/15412-f9a89b026e6774d1%40postgresql.or
On 03/05/2021 10:43, Laurenz Albe wrote:
On Sun, 2021-05-02 at 22:43 +0200, Adrien Nayrat wrote:
LOG: started streaming WAL from primary at AA/A100 on timeline 1
FATAL: could not receive data from WAL stream : ERROR: requested starting
point AA/A100 is ahead of the WAL flush position
rd, I don't understand how the secondary can miss the last 2
records of A0? It seems he did not received the CHECKPOINT_SHUTDOWN record?
Any idea?
Thanks!
--
Adrien NAYRAT
om/ClusterLabs/resource-agents/blob/master/heartbeat/pgsql
- PAF : http://clusterlabs.github.io/PAF/ (Which is different from pgsql RA :
http://clusterlabs.github.io/PAF/FAQ.html#why-new-ra-for-postgresql)
If I am right, PAF should handle the case when there no need to perform pgrewind
(if the
Hello,
FYI, check_pgactivity has a service to detect frozen stat collector:
https://github.com/OPMDG/check_pgactivity#user-content-stat_snapshot_age-9.5
We added this service after a customer has deactivated IPv6 that broke stat
collector.
Regards,
signature.asc
Description: OpenPGP digital s
On 6/7/19 12:19 PM, Tasks wrote:
> 😢 is there a solution to that?
> Is it possible that we add it ourselves ???
>
> Has anyone worked with this extension ->
> https://github.com/postgrespro/snowball_ext
>
> Tassos
>
I did not played with this extension, maybe you can add greek to
https://git
On 6/7/19 10:31 AM, Tasos wrote:
> Hi to all,
>
> Since Oct 2018 -
> Greekhttps://www.postgresql.org/message-id/E1g4YQa-0003tf-Gr%40gemulon.postgresql.org
> stemming algorithm contributed by Oleg Smirnov is in
> inclued in the Snowball project.
>
> I believe it can be included in the Release
Hello,
On 11/10/18 12:49 AM, Jean-Marc Lessard wrote:
> The dumped table is 0.5TB, 17 million rows and LOB uses about 99% of the
> space.
>
If I understand, you have 17 million Large Object?
I do not recall exactly and maybe I am wrong. But it seems pg_dump has to
allocate memory for each obje
On 11/7/18 1:21 PM, Alexandre Arruda wrote:
The best solution that I have found is kick all connections and execute
a select for update to /dev/null in the affected tables, i.e.:
psql -o /dev/null -c "select * from table for update" database
After this, the vacuum is executed w/o problems agai
On 11/5/18 5:41 PM, Adrien NAYRAT wrote:
We "solved" with a dump/restore on another server, also we kept previous
cluster to investigate. I want to be sure we encountered the bug solved
in 9.6.9 and it is not a new one.
FYI, I am not sure I will be able to keep previous cluster
On 6/8/18 8:30 PM, Jeremy Finzel wrote:
No I was referring to this from the documentation:
Avoid spuriously marking pages as all-visible (Dan Wood, Pavan
Deolasee, Álvaro Herrera)
This could happen if some tuples were locked (but not deleted).
While queries would still functi
On 08/08/2018 04:09 PM, czezz wrote:
Hi everyone,
I want to aks if anyone knows is there a way to search for specific
"value" throughout list of tables OR all tables in databse?
Cheers,
czezz
Hello,
Maybe this article by Daniel could help you :
https://blog-postgresql.verite.pro/2017/06/06
On 07/18/2018 10:26 AM, Hans Schou wrote:
Am I doing something wrong or should some history be cleared?
Hi,
FIY, check_pgactivity save the diff between each call to compute the
real hit ratio : https://github.com/OPMDG/check_pgactivity
Regards,
On 07/16/2018 11:50 PM, Alessandro Aste wrote:
> Thanks much, I'll check that out. I see the queries are 3 years old so I'm
> wondering if they still work for 9.6.x or 10
AFAIK they work. You can try yourself by comparing bloated table/index size
before and after vacuum full or reindex ;)
sig
On 07/16/2018 05:16 PM, Alessandro Aste wrote:
Hello, I am trying to put togheter a query to monitor the index bloat
for a database I maintain.
Is there a "SQL" way to obtain bloated index ? I googled around but I
found nothing working.
I'm currently running 9.6 but I'm looking for something
On 06/27/2018 09:58 AM, Andreas Joseph Krogh wrote:
>
> but we have to settle on a way of controlling it.
+1 from me.
I am running more and more into situations where people consider
this a bug rather than a feature.
FWIW, I think a GUC that switches between the curre
u know.. But looks like it uses the
> same
> INSERT, not copy.. interesting if it runs quick on my machine.
Yes it use INSERT, maybe it is not difficult to change the code to use COPY
instead.
--
Adrien NAYRAT
https://blog.anayrat.info
signature.asc
Description: OpenPGP digital signature
t;
> Thanks,
> Anto.
Hello Anto,
I used this tool :
https://github.com/Networks-Learning/stackexchange-dump-to-postgres
Regards,
--
Adrien NAYRAT
https://blog.anayrat.info
signature.asc
Description: OpenPGP digital signature
ll add an entry in september's commit fest.
>
> excellent. Exactly what I want!
FYI, I added an entry in next commit fest (september is not open) :
https://commitfest.postgresql.org/18/1691/
Feel free to review it ;)
Regards,
--
Adrien NAYRAT
signature.asc
Description: OpenPGP digital signature
On 06/20/2018 03:08 PM, Andreas Kretschmer wrote:
> I would suggest using of pg_stat_statements for that.
I agree, but sometimes it is not sufficient. For example, if you need query's
parameters.
--
Adrien NAYRAT
signature.asc
Description: OpenPGP digital signature
On 06/20/2018 01:51 PM, Janning Vygen wrote:
Back in 2009 I made a suggestion which is not implemented yet but would
still be very valuable and easy to implement in my opinion (not for me
as I am not speaking C):
https://www.postgresql.org/message-id/flat/200903161426.56662.vygen%40kicktipp.de
'_confirm_stopped: instance "%s" controldata indicates that the
instance was propertly shut down',
$OCF_RESOURCE_INSTANCE );
return $OCF_NOT_RUNNING;
}
Regards,
--
Adrien NAYRAT
signature.asc
Description: OpenPGP digital signature
pacemaker :
PCMK_debug=crmd,pengine,lrmd
This should give you more information in logs. Monitor action in PAF should
report why the cluster doesn't start :
https://github.com/ClusterLabs/PAF/blob/master/script/pgsqlms#L1525
Regards,
--
Adrien NAYRAT
signature.asc
Description: OpenPGP digital signature
28 matches
Mail list logo
