Re: BUG #18779: Segmentation fault while trying to connect via psql

From: Даниил Элишаков <dan-eli(at)mail(dot)ru>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18779: Segmentation fault while trying to connect via psql
Date: 2025-01-22 08:28:53
Message-ID: 1737534533.668379460@f748.i.mail.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Here is a gif with bug scenario. Gif starts while already being switched to root user. The phrase ‘’Ошибка сегментирования’’ stands for Segmentation fault. Sorry for mixing up the issue and it’s possible causes in the previous letter. Hope this gif will make it clear
 
Regards,
Daniil 
>Воскресенье, 19 января 2025, 5:32 +03:00 от Jeff Janes <jeff(dot)janes(at)gmail(dot)com>:

>On Fri, Jan 17, 2025 at 6:51AM PG Bug reporting form < noreply(at)postgresql(dot)org > wrote:
>>The following bug has been logged on the website:
>>
>>Bug reference:      18779
>>Logged by:          Daniel Elishakov
>>Email address:      dan-eli(at)mail(dot)ru
>>PostgreSQL version: 16.6
>>Operating system:   Debian GNU/Linux 12 (bookworm)
>>Description:       
>>
>>This bug takes place in Debian-based operating systems. To replicate this
>>bug please do following:
>>1) Install and initialize PostgreSQL dbms

>I think we need more details. There are multiple ways to do both of those things.

>>2) Switch user to root (sudo -i)
>>3) Switch user to postgres

>What if you just use one command, sudo -i -u postgres?

>>4) run command psql -U postgres -h localhost (may run multiple times to see
>>the bug)
>>
>>Looks like this bug occurs because root user has ENV variable KRB5CCNAME,
>>while postgres does not.

>What did you do to make this happen?  A default debian installation does have KRB5CCNAME set for root.

>Cheers,

>Jeff
 
 
С уважением,
Даниил Элишаков
dan-eli(at)mail(dot)ru
 

Attachment Content-Type Size
bug_seg_fault.gif image/gif 483.5 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris BSomething 2025-01-22 10:00:04 Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
Previous Message Tom Lane 2025-01-21 17:04:56 Re: Combining array slicing and indexing causes incorrect/confusing results