Changed test case slightly so it doesn't have an unused typedef.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/84a05d479e7d1287caaca24a36b30d62cdc78924
Modified Files
--
src/interfaces/ecpg/test/expected/preproc-define.c | 22
.../
Changed test case slightly so it doesn't have an unused typedef.
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/c142a1acf7fa30cc423c01a9409a5e26cbf9ed87
Modified Files
--
src/interfaces/ecpg/test/expected/preproc-define.c | 22 --
Changed test case slightly so it doesn't have an unused typedef.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f2d6bdf8480bf4f3ecd787a8b02e393860bf824b
Modified Files
--
src/interfaces/ecpg/test/expected/preproc-define.c | 22 --
Changed test case slightly so it doesn't have an unused typedef.
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/5f8f8cbec59a4ccc7add72757b6fdcaa7e889e6f
Modified Files
--
src/interfaces/ecpg/test/expected/preproc-define.c | 22 --
Changed test case slightly so it doesn't have an unused typedef.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/4c412ca2e510ecde00e36d226ff933acd6fb477a
Modified Files
--
src/interfaces/ecpg/test/expected/preproc-define.c | 22 --
Michael Meskes writes:
> Changed test case slightly so it doesn't have an unused typedef.
> Branch
> --
> REL8_4_STABLE
Hm, why no patch in 9.0?
regards, tom lane
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your su
Changed test case slightly so it doesn't have an unused typedef.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/da174fb0390e9827d7a76d43a7f3cab632d52dc0
Modified Files
--
src/interfaces/ecpg/test/expected/preproc-define.c | 22 --
On Sun, Nov 03, 2013 at 09:53:33AM -0500, Tom Lane wrote:
> Hm, why no patch in 9.0?
Stupid me, no idea what happened with 9.0. Shell history shows that I switched
to 9.0 but not run the cherry-pick. Fixed. Thanks.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De
Prevent memory leaks from accumulating across printtup() calls.
Historically, printtup() has assumed that it could prevent memory leakage
by pfree'ing the string result of each output function and manually
managing detoasting of toasted values. This amounts to assuming that
datatype output functi
Prevent memory leaks from accumulating across printtup() calls.
Historically, printtup() has assumed that it could prevent memory leakage
by pfree'ing the string result of each output function and manually
managing detoasting of toasted values. This amounts to assuming that
datatype output functi
Prevent memory leaks from accumulating across printtup() calls.
Historically, printtup() has assumed that it could prevent memory leakage
by pfree'ing the string result of each output function and manually
managing detoasting of toasted values. This amounts to assuming that
datatype output functi
Get rid of more cases of the "must detoast before output function" meme.
I missed that json.c was doing this too, because for some bizarre reason
it wasn't doing it adjacent to the output function call.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e36ce0c7f7b329b2
12 matches
Mail list logo
