From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Björn Lundin <b(dot)f(dot)lundin(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Order by and timestamp |
Date: | 2020-03-16 23:20:04 |
Message-ID: | 20195383-f8ae-9b48-9a8e-dd19f6efb8b4@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/16/20 2:50 PM, Björn Lundin wrote:
>
> But not for that data sep/oct 2016
Had a thought, what if on the ibm2 machine you do:
UPDATE amarkets SET startts = '2016-09-30 13:00:00' WHERE
marketid = 1.127278857;
And then rerun:
select * from amarkets order by startts;
>
>
>> Yes really, otherwise you would not be seeing a difference. Sorry, pet
>> peeve of mine, when people say these two things are not doing the same
>> thing but then say they are the same thing.
>>
>>> I mean, the pg_dump does copy-commands.
>>
>> It also does a certain amount of setup at the beginning of the file.
>
> I stand corrected
>
> --
> Björn Lundin
> b(dot)f(dot)lundin(at)gmail(dot)com <mailto:b(dot)f(dot)lundin(at)gmail(dot)com>
>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Smith | 2020-03-17 05:56:48 | Re: Invalid byte sequence errors on DB restore |
Previous Message | Adrian Klaver | 2020-03-16 22:21:34 | Re: Order by and timestamp |