Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2 - Mailing list pgsql-general

From Jim Nasby
Subject Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2
Date
Msg-id 237f449f-9a69-6027-1c1b-4b1acee372d9@BlueTreble.com
Whole thread Raw
In response to Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2  (David Gibbons <david@dgibbons.net>)
Responses Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2  (Patrick B <patrickbakerbr@gmail.com>)
Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
On 9/8/16 3:29 PM, David Gibbons wrote:
>
>     Isn't this heading in the wrong direction?   We need to be more
>     precise than 0 (since 0 is computed off of rounded/truncated time
>     stamps), not less precise than 0.
>
>     Cheers,
>
>     Jeff
>
>
>
> Hmm, You may be right, reading it 4 more times for comprehension it
> looks like it should be set to -1 not 1.

Not according to my man page:

        --modify-window
               When comparing two timestamps, rsync treats the
timestamps as being equal if they differ by no more than the
modify-window value.  This is normally 0 (for an exact match), but you
               may find it useful to set this to a larger value in some
situations.  In particular, when transferring to or from an MS Windows
FAT  filesystem  (which  represents  times  with  a
               2-second resolution), --modify-window=1 is useful
(allowing times to differ by up to 1 second).

--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461


pgsql-general by date:

Previous
From: Kiran
Date:
Subject: Re: Trigger is not working for Inserts from the application
Next
From: Jim Nasby
Date:
Subject: Re: Trigger is not working for Inserts from the application