pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Segmentation Fault (Logical Replication)
3+ messages / 3 participants
[nested] [flat]

* Segmentation Fault (Logical Replication)
@ 2020-01-29 12:22 M Rehman Kahloon <m.rehman@3gca.org>
  2020-01-29 15:25 ` Re: Segmentation Fault (Logical Replication) Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: M Rehman Kahloon @ 2020-01-29 12:22 UTC (permalink / raw)
  To: pgsql-bugs

Hi

 

          I am facing very critical issue with my master database when
implemented logical replication using pglogical and built in replication
feature ( publisher using postgrSQL 10 and subscription using PostgreSQL
11). 

 

DB crashing frequently with error 'Segmentation Fault' error.  Same issue
when seeting pg-wal logical and replica.

 

Please need your kind response to sort out issue. 

 

Your sincerely

 

Mr Kahloon

Senior Data ANALYST.

 

 

 

 

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Segmentation Fault (Logical Replication)
  2020-01-29 12:22 Segmentation Fault (Logical Replication) M Rehman Kahloon <m.rehman@3gca.org>
@ 2020-01-29 15:25 ` Tom Lane <tgl@sss.pgh.pa.us>
  2020-01-30 02:30   ` Re: Segmentation Fault (Logical Replication) Michael Paquier <michael@paquier.xyz>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2020-01-29 15:25 UTC (permalink / raw)
  To: M Rehman Kahloon <m.rehman@3gca.org>; +Cc: pgsql-bugs

"M Rehman Kahloon" <m.rehman@3gca.org> writes:
>           I am facing very critical issue with my master database when
> implemented logical replication using pglogical and built in replication
> feature ( publisher using postgrSQL 10 and subscription using PostgreSQL
> 11). 
> DB crashing frequently with error 'Segmentation Fault' error.  Same issue
> when seeting pg-wal logical and replica.

There's nowhere near enough information in this report for anyone to
help you.  Please see

https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

and

https://www.postgresql.org/docs/11/bug-reporting.html

for some advice about what to put in a useful trouble report.
Since you're getting crashes, we'd probably also wish to see
a stack trace,

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Segmentation Fault (Logical Replication)
  2020-01-29 12:22 Segmentation Fault (Logical Replication) M Rehman Kahloon <m.rehman@3gca.org>
  2020-01-29 15:25 ` Re: Segmentation Fault (Logical Replication) Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-01-30 02:30   ` Michael Paquier <michael@paquier.xyz>
  0 siblings, 0 replies; 3+ messages in thread

From: Michael Paquier @ 2020-01-30 02:30 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: M Rehman Kahloon <m.rehman@3gca.org>; pgsql-bugs

On Wed, Jan 29, 2020 at 10:25:38AM -0500, Tom Lane wrote:
> for some advice about what to put in a useful trouble report.
> Since you're getting crashes, we'd probably also wish to see
> a stack trace,
> 
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

Impossible to say if that's Postgres problem without at least a
backtrace (even better a reproducible scenario), but you could also
consider contacting the maintainers of pglogical:
https://github.com/2ndQuadrant/pglogical
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2020-01-30 02:30 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-01-29 12:22 Segmentation Fault (Logical Replication) M Rehman Kahloon <m.rehman@3gca.org>
2020-01-29 15:25 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-01-30 02:30   ` Michael Paquier <michael@paquier.xyz>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox