Nope, I installed v4.1.3 and it is the same, pg_default appears as the
tablespace. Even when I use the drop down list in the right pane of PgAdmin
to select the my_space tablespace, and then click the Save button, it does
not change.
--
View this message in context:
Postgres version is 9.4
PgAdmin version is 1.0
The value returned by the suggested query is correctly reported as
'my_space'.
--
View this message in context:
http://www.postgresql-archive.org/Tablespace-Default-Behavior-tp5952910p5953046.html
Sent from the PostgreSQL - general mailing list
In PgAdmin, when I right-click the table, in the Properties pane on the right
side of the screen, the tablespace is listed as "pg_default"
--
View this message in context:
http://www.postgresql-archive.org/Tablespace-Default-Behavior-tp5952910p5953028.html
Sent from the PostgreSQL - general
That is what I suspected, and thank you for the explanation. I think it is
misleading and a bug in PgAdmin for explicitly listing the tablespace as
pg_default.
--
View this message in context:
http://www.postgresql-archive.org/Tablespace-Default-Behavior-tp5952910p5952929.html
Sent from the
More Info Edit: Also, the database is in the my_space tablespace. The
location for the my_space tablespace is a different folder than the $PGDATA
folder.
--
View this message in context:
http://www.postgresql-archive.org/Tablespace-Default-Behavior-tp5952910p5952917.html
Sent from the
I am somewhat new to Postgresql. I cant seem to create a table in a
non-default tablespace. In the postgresql.conf file, I have:
default_tablespace = ''".
When I create a table, like this:
CREATE TABLE myschema.mytable (rc_id integer NOT NULL) TABLESPACE
my_space;
and then I do:
Thank you all. You have given me a lot to digest for my project.
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5831358.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general
Some more questions if you please. I am in Houston, and we don't have a
postgres users group. If anyone knows of some postgres groups that have
webcasts of their meetings, let me know. Thanks.
I am trying to figure out how to manage the SSL client certificates in a
Windows 7 environment, both
I am developing a Windows desktop application so the client is the desktop
application. Depending on the installation, the app will be running in
single user mode, with the server and client both on only one machine, using
127.0.0.1. In that type of installation, there is little or no reason the
Right, I want to try connecting by psql, but the postgres documentation and
psql -- help do not list the syntax for providing the certificate. I
tried the following, but the error was : Connection requires a valid
certificate
$
O.K. I just found the environment variables for SSL, described in Man 31.14.
I will try that.
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5830961.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
Trying to connect via psql, I looked at the documentation and around the web,
but could not find the right syntax for including all the SSL connection
variables on the psql command line. I tried using the URL-type psql
command, variations of this:
Unless I am missing something, I still do not see where how / where to
specify sslcert, sslkey, root.crt in the psql command. The referenced links
don't much go beyond these input variables [ dbname [ username ] [ host ] [
port ] .
--
View this message in context:
I understand all of that, about certificates. I only included all of the
pg_env.bat file for completeness. You understand that I am trying to
connect to the database by using just psql?
--
View this message in context:
Yes, I have tested that the connection and it does work without SSL. I have
also verified with openssl that all the certificates have the same CN,
issuer, etc.
I am working in a development environment, hence the seemingly odd file
location. It may not seem that way, but I am narrowing down
To anyone following this thread, I would also like to point out the
following, from Man 31.18.1.
In verify-full mode, the cn (Common Name) attribute of the certificate is
matched against the host name. If the cn attribute starts with an asterisk
(*), it will be treated as a wildcard, and will
Thank you. That resolved it. After revising the certificates, I was able to
connect with psql. I really appreciate all the help.
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5831051.html
Sent from the PostgreSQL - general
I am trying to connect using SSL in Windows 7 and Postgres v9.3. The console
output error message is Failed to establish a connection to 127.0.0.1 The
error message from the pg_log is:
---
2014-12-15 19:20:24 GMT FATAL: connection requires
Yes, I set the CN to 127.0.0.1 for all certificates. I verified that for all
certificates using openssl verify. I can connect o.k. without the SSL.
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5830768.html
Sent from the
I changed the CN in all the certificates from 127.0.0.1 my_role, which is
the user id. Now the pg_log contains this:
---
2014-12-15 22:28:04 GMT LOG: database system was shut down at 2014-12-15
22:28:01 GMT
Yes, I did intend for only SSL connections. The console app must be the
SYSTEM user then, directly or maybe indirectly through the Windows
Certificate Store. I already added root.crt to the trusted certificates
through Windows MMC. Here is my console app, in which I provide the
certificate, so
Thank you all. Would something like Wireshark, WinPcap or WFetch show me
more about the SYSTEM connection?
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5830806.html
Sent from the PostgreSQL - general mailing list archive at
Ah! I figured out the pg_log error about No pg_hba.conf entry for host
127.0.0.1, user SYSTEM, database postgres, SSL off. That error
occurs when I go into Windows Component Services and restart postgres.
But, after I delete that pg_log file, there still is no connection and no
other pg_log
As suggested, I changed the data folder permissions from Read Only to allow
Read / Write (I was already logged in as Administrator), but the errors are
the same.
If I remove the SSL-related lines in pg_hba.conf and postgresql.conf, and
use the following lines instead in pg_hba.conf, I am able
Windows automatically changed the data folder attribute back to Read Only.
The only Windows groups that have full permission are SYSTEM, Administrators
and my administrator /user account.
--
View this message in context:
I am trying to implement SSL certificates with postgres 9.3 locally in
Windows 7. In Windows Component Services / Local Services, postrgres is
configured to start automatically, with Log On as a local system account.
Using my Windows administrator account, in a command prompt inside my data
26 matches
Mail list logo
