Hi guys,
the link to the "Docbook DSSSL Stylesheets"
(http://docbook.sourceforge.net/projects/dsssl/index.html) in the
Documentation Appendix, section Tool sets is broken.
You can test the link from here:
http://www.postgresql.org/docs/current/static/docguide-toolsets.html
Some of the p
Aggro napsal(a):
I think all information is collected and they are
used for all pg_dump run. It
does not make sense to free them. See line 725.
Zdenek
But is the memory freed at some point? E.g. when
program shuts down? If it is not freed ever, then it
is a memory leak. I'm i
[EMAIL PROTECTED] napsal(a):
The following bug has been logged online:
Bug reference: 4494
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: Latest cvs
Operating system: Error in source code
Description:Memory leak in pg_regress.c
Details:
In file
On Thursday 30 October 2008, Tomáš Szépe wrote:
> > A pg_dump run is comparatively short-lived, so if Zdenek is right then
> > there's no important leak here -- we're counting on program exit to
> > release the memory. There's probably little point in releasing things
> > earlier than that.
>
> W
The following bug has been logged online:
Bug reference: 4508
Logged by: dta
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: Vista (windows 2008)
Description:bug #4389 could not reattach to shared memory
Details:
Hi,
when I follow the adv
>>> Francisco Olarte Sanz <[EMAIL PROTECTED]> wrote:
> Similarly nearly nobody bothers
> to fclose() stdin/out/err
On that one, maybe it should be done more often. In writing
pg_clearxlogtail I found that closing stdout improved performance
markedly. This was a filter piping from disk into gz
Zdenek,
> Harvey, Allan AC napsal(a):
> > Zdenek,
> >
> >> Hmm, It does not look good. Your OS does not return proper
> >> information about
> >> codeset. Following code is broken:
> >>
> >>setlocale(LC_CTYPE, ctype);
> >>sys = nl_langinfo(CODESET);
> >>sys = strdup(sys);
> >>
> >>
