On 4/10/24 1:31 PM, Tom Lane wrote:
Adrian Klaver writes:
On 4/10/24 12:38, Adnan Dautovic wrote:
By the way, the row count of pg_timezone_names is 385, but I do
not know how that compares to a more standard installation.
On my instance of Postgres 16.2, 1196.
You're probably using a
Adrian Klaver writes:
> On 4/10/24 12:38, Adnan Dautovic wrote:
>> By the way, the row count of pg_timezone_names is 385, but I do
>> not know how that compares to a more standard installation.
> On my instance of Postgres 16.2, 1196.
You're probably using a build with --with-system-tzdata
Adnan Dautovic writes:
> On 05. Apr 2024, at 16:13, Tom Lane wrote:
>> Out of curiosity, does
>> SET timezone to 'GMT';
>> work?
> Yes, it yields:
>> SET
>>
>> Query returned successfully in 84 msec.
I expected that, because the name "GMT" is hard-wired in our code.
Doesn't help for
On 4/10/24 12:38, Adnan Dautovic wrote:
Hi,
On 05. Apr 2024, at 16:13, Tom Lane wrote:
Adnan Dautovic writes:
By the way, the row count of pg_timezone_names is 385, but I do
not know how that compares to a more standard installation.
On my instance of Postgres 16.2, 1196.
Kind
Dear Adrian,
On 05. Apr 2024, at 17:05, Adrian Klaver wrote:
The below is cut down from the actual output as there should be at least:
Europe/Berlin CEST 02:00:00 t
present also?
Correct! That entry also exists. I only included the snippet
where I would have expected the "UTC" entry to
Hi,
On 05. Apr 2024, at 16:13, Tom Lane wrote:
Adnan Dautovic writes:
SELECT * FROM pg_timezone_names ORDER BY name;
"name""abbrev" "utc_offset" "is_dst"
"Turkey" "+03" "03:00:00"false
"UCT" "UCT" "00:00:00"false
"Universal" "UTC" "00:00:00"false
"W-SU"
On 4/5/24 02:39, Adnan Dautovic wrote:
Dear Adrian,
Adrian Klaver wrote:
Define 'read-only', especially as it applies to the privileges on the
public schema.
I am not quite sure which information you are looking for
exactly. According to this [1], I ran the following query:
WITH
Adnan Dautovic writes:
> However, this lead me to [2] and I find the output very
> interesting:
> SELECT * FROM pg_timezone_names ORDER BY name;
>> "name" "abbrev""utc_offset""is_dst"
>> "Turkey" "+03" "03:00:00" false
>> "UCT""UCT" "00:00:00" false
Dear Adrian,
Adrian Klaver wrote:
Define 'read-only', especially as it applies to the privileges on the
public schema.
I am not quite sure which information you are looking for
exactly. According to this [1], I ran the following query:
WITH "names"("name") AS (
SELECT n.nspname AS "name"
Hi Tom,
thank you for your reply!
Tom Lane wrote:
You realize of course that PG 9.4.x is four years past EOL, and that
the last release in that series was 9.4.26, so that your remote is
missing three or so years' worth of bug fixes even before its EOL.
The underlying macOS platform looks a
On 4/3/24 22:23, Adnan Dautovic wrote:
Hi everyone,
I have some trouble using postgres_fdw in order to display some data from a
Postgres database I do not control in a Postgres database that I do control. I
filled out the form from the wiki below and would appreciate any tips.
* A
Adnan Dautovic writes:
> I have some trouble using postgres_fdw in order to display some data from a
> Postgres database I do not control in a Postgres database that I do control.
Hmm ...
> * PostgreSQL version number you are running:
> remote: "PostgreSQL 9.4.13 on x86_64-apple-darwin20.2.0,
Hi everyone,
I have some trouble using postgres_fdw in order to display some data from a
Postgres database I do not control in a Postgres database that I do control. I
filled out the form from the wiki below and would appreciate any tips.
* A description of what you are trying to achieve and
13 matches
Mail list logo
