On Mon, Jun 26, 2017 at 12:25 PM, tushar <tushar.ah...@enterprisedb.com> wrote:
> Hi,
> While trying to do - make of pg_filedump against v10 sources , getting an
> errors
> [centos@centos-cpula pg_filedump]$ make
> cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -DLINUX_OOM_ADJ=0 -Wall
> -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement
> -Wendif-labels -fno-strict-aliasing -fwrapv
> -I/home/centos/pg10_/postgresql/src/include/ pg_filedump.c -c
> pg_filedump.c: In function ‘FormatControl’:
> pg_filedump.c:1650: error: ‘ControlFileData’ has no member named
> ‘enableIntTimes’
> make: *** [pg_filedump.o] Error 1
> [centos@centos-cpula pg_filedump]$

That's because the following git commit in v10 has removed
'enableIntTimes' member from 'ControlFileData' structure,

commit d28aafb6dda326688e2f042c95c93ea57963c03c
Author: Tom Lane <t...@sss.pgh.pa.us>
Date:   Thu Feb 23 12:23:12 2017 -0500

    Remove pg_control's enableIntTimes field.

    We don't need it any more.

    pg_controldata continues to report that date/time type storage is
    "64-bit integers", but that's now a hard-wired behavior not something
    it sees in the data.  This avoids breaking pg_upgrade, and perhaps other
    utilities that inspect pg_control this way.  Ditto for pg_resetwal.

    I chose to remove the "bigint_timestamps" output column of
    pg_control_init(), though, as that function hasn't been around long
    and probably doesn't have ossified users.

    Discussion: https://postgr.es/m/26788.1487455...@sss.pgh.pa.us

I think we will have change pg_filedump such that it no more refers to

With Regards,
Ashutosh Sharma

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to