Closed dpage closed 2 years ago
Attachment migrated from Redmine: https://redmine.postgresql.org/attachments/download/1930 Originally created by AMOS Operation at 2017-01-11 13:53:13 UTC.
Attachment migrated from Redmine: https://redmine.postgresql.org/attachments/download/1931 Originally created by AMOS Operation at 2017-01-11 13:53:13 UTC.
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-3 Originally created by Khushboo Vashi at 2017-01-13 05:01:19 UTC.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Status changed | New | In Progress |
Assigned To changed | Khushboo Vashi |
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-4 Originally created by Khushboo Vashi at 2017-01-13 06:43:14 UTC.
The patch submitted.
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-5 Originally created by AMOS Operation at 2017-01-13 08:16:28 UTC.
Thank you !
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-6 Originally created by Khushboo Vashi at 2017-01-27 11:55:37 UTC.
The updated patch submitted.
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-7 Originally created by Khushboo Vashi at 2017-02-03 10:46:12 UTC.
Applied in changeset commit:f2ac6fc6a79a4e9d6418d89aaec38d0576f8a054.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Status changed | In Progress | In Testing |
Done Ratio changed | 0 | 90 |
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-8 Originally created by Fahar Abbas at 2017-02-06 05:00:03 UTC.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Status changed | In Testing | Resolved |
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-9 Originally created by Fahar Abbas at 2017-02-06 05:00:15 UTC.
This issue is resolved and tested against following commit:
commit 4566877188b3e41caa3a2a786a930c98f8d1d40e
Tested Platform: MAC 10.9(Python 3.5) Windows 2012 server 64(Python 2.7.11) Centos 6.5 64(Python 2.7.5)
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-10 Originally created by mary masterson at 2017-03-30 17:23:00 UTC.
On Windows 10, I installed PgAdmin v4.1.3 and pg_default incorrectly appears as the tablespace. See "Tablespace Default Behavior" discussion in Postgresql - General forum. 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.
Comment migrated from Redmine: https://redmine.postgresql.org/issues/2069#note-11 Originally created by Fahar Abbas at 2018-01-09 04:46:08 UTC.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Done Ratio changed | 90 | 100 |
Issue closed on Redmine.
Issue migrated from Redmine: https://redmine.postgresql.org/issues/2069 Originally created by AMOS Operation at 2017-01-11 13:53:20 UTC.
Version : 1.1 Python Version : 2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:19:22) [MSC v.1500 32 bit (Intel)] Flask Version : 0.11.1 Application Mode : Desktop
I have created a database "testenv" on a tablespace "testenv_data". The tables are then created without specifying a tablespace : so they are stored in testenv_data. In PGadmin 4, we can see in the table properties that all tables of "testenv" are stored in pg_default, which is wrong. In PGadmin 3 it displays the correct tablespace.