From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?B?c3F1aWQgd2FyZA==?= <squidw@mail.ru>
cc: pgsql-interfaces@lists.postgresql.org
Subject: Re: =?UTF-8?B?ZGlyZWN0b3J5IG5hbWUgZXF1YWwgZGF0YWJhc2UgbmFtZQ==?=
In-reply-to: <1580814072.863026304@f532.i.mail.ru>
References: <1580814072.863026304@f532.i.mail.ru>
Comments: In-reply-to =?UTF-8?B?c3F1aWQgd2FyZA==?= <squidw@mail.ru>
	message dated "Tue, 04 Feb 2020 14:01:12 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7028.1580833215.1@sss.pgh.pa.us>
Date: Tue, 04 Feb 2020 11:20:15 -0500
Message-ID: <7029.1580833215@sss.pgh.pa.us>
Precedence: bulk

=?UTF-8?B?c3F1aWQgd2FyZA==?= <squidw@mail.ru> writes:
> Question is why directory name not equal as database name?

Because (1) it doesn't work for database names that aren't legal as
filenames (according to the none-too-well-standardized rules of your
particular filesystem); (2) SQL requires us to treat "FOO" and "foo"
as distinct names, but the filesystem might not; (3) renaming a database
is dangerous, as there's no way to make the directory rename action
atomic with commit of the system catalog updates; (4) renaming a database
causes problems for concurrent sessions that might be in the middle of
opening files in that database.  And probably a few other reasons I
don't recall off the top of my head.

> Can i change it?

No.

			regards, tom lane