Horton

Re: SSL Tests for sslinfo extension

Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>

View thread View on postgr.es
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker )
To: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-19T17:01:58Z
Lists: pgsql-hackers 
Daniel Gustafsson <daniel@yesql.se> writes:

> In order to be able to test extensions with SSL connections, allow
> configure_test_server_for_ssl to create any extensions passed as
> comma separated list. Each extension is created in all the test
> databases which may or may not be useful.

Why the comma-separated string, rather than an array reference,
i.e. `extensions => [qw(foo bar baz)]`?  Also, should it use `CREATE
EXTENSION .. CASCADE`, in case the specified extensions depend on
others?

- ilmari
-- 
"The surreality of the universe tends towards a maximum" -- Skud's Law
"Never formulate a law or axiom that you're not prepared to live with
 the consequences of."                              -- Skud's Meta-Law

Commits

  1. Use test-specific temp path for keys during SSL test

  2. Add TAP tests for contrib/sslinfo

  3. Extend configure_test_server_for_ssl to add extensions