[COMMITTERS] pgsql: Add a stack overflow check to copyObject().

Add a stack overflow check to copyObject(). There are some code paths, such as SPI_execute(), where we invoke copyObject() on raw parse trees before doing parse analysis on them. Since the bison grammar is capable of building heavily nested parsetrees while itself using only minimal stack depth,

[COMMITTERS] pgsql: Add a stack overflow check to copyObject().

Add a stack overflow check to copyObject(). There are some code paths, such as SPI_execute(), where we invoke copyObject() on raw parse trees before doing parse analysis on them. Since the bison grammar is capable of building heavily nested parsetrees while itself using only minimal stack depth,

[COMMITTERS] pgsql: Add a stack overflow check to copyObject().

Add a stack overflow check to copyObject(). There are some code paths, such as SPI_execute(), where we invoke copyObject() on raw parse trees before doing parse analysis on them. Since the bison grammar is capable of building heavily nested parsetrees while itself using only minimal stack depth,

[COMMITTERS] pgsql: Add a stack overflow check to copyObject().

Add a stack overflow check to copyObject(). There are some code paths, such as SPI_execute(), where we invoke copyObject() on raw parse trees before doing parse analysis on them. Since the bison grammar is capable of building heavily nested parsetrees while itself using only minimal stack depth,

[COMMITTERS] pgsql: Add a stack overflow check to copyObject().

Add a stack overflow check to copyObject(). There are some code paths, such as SPI_execute(), where we invoke copyObject() on raw parse trees before doing parse analysis on them. Since the bison grammar is capable of building heavily nested parsetrees while itself using only minimal stack depth,

[COMMITTERS] pgsql: Add a stack overflow check to copyObject().

Add a stack overflow check to copyObject(). There are some code paths, such as SPI_execute(), where we invoke copyObject() on raw parse trees before doing parse analysis on them. Since the bison grammar is capable of building heavily nested parsetrees while itself using only minimal stack depth,

[COMMITTERS] pgsql: Allow the low level COPY routines to read arbitrary numbers of f

Allow the low level COPY routines to read arbitrary numbers of fields. This doesn't involve any user-visible change in behavior, but will be useful when the COPY routines are exposed to allow their use by Foreign Data Wrapper routines, which will be able to use these routines to read irregular CSV

[COMMITTERS] pgsql: Fix two typos, by Fujii Masao.

Fix two typos, by Fujii Masao. Branch -- master Details --- http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=95e42a2c2980003880dee622fc3bed0b03322542 Modified Files -- src/backend/access/transam/xlog.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(

[COMMITTERS] pgsql: Fix two typos, by Fujii Masao.

Fix two typos, by Fujii Masao. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e116bcf290ed699c4a7273c5d4b385d1fcea5aa0 Modified Files -- src/backend/access/transam/xlog.c |4 ++-- 1 files changed, 2 insertions(+), 2 del

[COMMITTERS] pgsql: Put only single space after "Sort Method:", for consistency

Put only single space after "Sort Method:", for consistency Branch -- master Details --- http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=951d7861212120571a601d946194892db6f2bde1 Modified Files -- src/backend/commands/explain.c |2 +- 1 files changed, 1 ins