Hi,
Starting postgres with a CWD that's not readable will trigger an Assert
and if those are disabled it presumably will segfault.
#0 0x775621e5 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x77565398 in __GI_abort () at abort.c:90
#2 0x
Andres Freund writes:
> Starting postgres with a CWD that's not readable will trigger an Assert
> and if those are disabled it presumably will segfault.
Yeah, we've discussed that before. I'm not sure it's worth fixing,
or that it could be counted on to stay fixed even if we removed the
current
On 2013-10-03 19:07:37 +0200, Tom Lane wrote:
> Andres Freund writes:
> > Starting postgres with a CWD that's not readable will trigger an Assert
> > and if those are disabled it presumably will segfault.
>
> Yeah, we've discussed that before. I'm not sure it's worth fixing,
> or that it could b
The following bug has been logged on the website:
Bug reference: 8498
Logged by: Regina Obe
Email address: l...@pcorp.us
PostgreSQL version: 9.3.0
Operating system: Windows 2003 x 64-bit
Description:
I noticed when restoring my 9.2 databases to 9.3 that my pg_trgm ext
Disregard my bug complaint. Stupid user error.
Thanks,
Regina
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
