On 2/7/19 3:24 PM, David G. Johnston wrote:
On Thursday, February 7, 2019, Steve Wampler mailto:swamp...@nso.edu>> wrote:
(1) the table already exist and the immediately doesn't exist?
(2) report ERROR on UPDATE when there are no UPDATES in the input file
Most likely the first
On Mon, Feb 11, 2019 at 12:29 PM Steve Wampler wrote:
> Thanks - but I thought the search_path update was a PG 10 change and so
> shouldn't reflect on 9.5.15 behavior. Did it
> get back-ported?
Yes, it was deemed a security vulnerability and thus back-patched.
Release notes will indicate when t
On Thursday, February 7, 2019, Steve Wampler wrote:
>
>(1) the table already exist and the immediately doesn't exist?
>(2) report ERROR on UPDATE when there are no UPDATES in the input file
>
Most likely the first attempt was schema qualified and so found the
existing targets table whil
With PostgreSQL 9.5.15, I ran:
pg_dump -t targets -d atst.experimentdb >nT.db
then I ran:
psql -h langley atst.experimentdbQUERY: UPDATE targets SET time_stamp=new.time_stamp,modified=new.modified,
id=new.id,targets=new.targets WHERE (id=new
On 2/7/19 9:28 AM, Steve Wampler wrote:
With PostgreSQL 9.5.15, I ran:
pg_dump -t targets -d atst.experimentdb >nT.db
then I ran:
psql -h langley atst.experimentdb
...
ERROR: relation "targets" already exists
ALTER TABLE
ERROR: relation "targets" does not exist
LINE
