< 	  returns in data?
> 	  returns in data

This prevents the next psql prompt from showing up on the end of the
last history line.

Devrim GUNDUZ

< * Make log_min_duration_statement output when the duration is reached rather
<   than when the statement completes
<
<   This prints long queries while they are running, making trouble shooting
<   easier.  Also, it eliminates the need for log_statement because it
<   would now be the same as a log_min_duration_statement of zero.

> * Make log_min_duration_statement output when the duration is reached rather
>   than when the statement completes
>
>   This prints long queries while they are running, making trouble shooting
>   easier.  Also, it eliminates the need for log_statement because it
>   would now be the same as a log_min_duration_statement of zero.

reliably (ie, regardless of which libraries they depend on).  Also
make sure that we don't select headers that obviously belong to the
wrong one of the two libraries.  This was discussed back around 4-Sep
but seems to have slipped through the cracks.  The header selection
could be checked more closely, perhaps, but let's see if this is good
enough.

< you would like to work on an item, please read the developer's FAQ
> you would like to work on an item, please read the Developer's FAQ

9c5
< Last updated:		Mon Nov 29 23:33:09 EST 2004
> Last updated:		Tue Nov 30 00:03:37 EST 2004
13a10,16
> #A hyphen, "-", marks changes that will appear in the upcoming 8.1 release.#
>
> Bracketed items, "[]", have more detail.
>
> This list contains all known PostgreSQL bugs and feature requests. If
> you would like to work on an item, please read the developer's FAQ
> first.

> * Prevent INET cast to CIDR from droping netmask, SELECT '1.1.1.1'::inet::cidr

> 	o Allow COPY FROM ... CVS to interpret newlines and carriage
> 	  returns in data?
>
> 	  This would require major refactoring of the copy source code.

> * Improve NLS maintenace of libpgport messages linked onto applications
>

so that they will be translatable.  Give messages some semblance of
conformance to the style guide.

<
> * Allow cross-compiling by generating the zic database on the target system

useful than just \'failed\' when there's a problem.  Per gripe from
Chris Albertson.

In an unrelated change, use VACUUM FULL; VACUUM FREEZE; rather than
a single VACUUM FULL FREEZE command, to respond to my worries of a
couple days ago about the reliability of doing this in one go.

Devrim GUNDUZ

    /*
     *  Some compilers with throw a warning knowing this test can never be
     *  true because off_t can't exceed the compared maximum.
     */
    if (th->fileLen > MAX_TAR_MEMBER_FILELEN)
        die_horribly(AH, modulename, "archive member too large for tar format\n");

> * Auto-vacuum
> 	o Move into the backend code
> 	o Scan the buffer cache to find free space or use background writer
> 	o Use free-space map information to guide refilling

Euler Taveira de Oliveira

initdb, and display in a path-native way.

prevents problems when the DECLARE is in a portal and is executed
repeatedly, as is possible in v3 protocol.  Per analysis by Oliver
Jowett, though I didn't use his patch exactly.

<   information, either by name or offset from UTC
>   information, either zone name or offset from UTC
>
>   If the TIMESTAMP value is stored with a time zone name, interval
>   computations should adjust based on the time zone rules, e.g. adding
>   24 hours to a timestamp would yield a different result from adding one
>   day.
>

who use it scan the relevant source files for their own catalog.  It
creates a bit of duplicate work for translators, but it gets the job done
for now.

by Troels Arvin, Simon Riggs, Elein Mustain

Make spelling of SQL standard names uniform.

integration.  It is much better to create a word list of unstemmed words
than stemmed ones.

Chris K-L

8.4.1).  This corrects some curious regex bugs, though not the greediness
issue I was hoping to find a solution for :-(

error conditions during regexp compile, but not during regexp execution;
any sort of "can't happen" errors would be treated as no-match instead
of being reported as they should be.  Noticed while trying to duplicate
a reported Tcl bug.

to be processed by GUC before InitPostgres, because any required lookup
of the encoding conversion function has to be done during InitializeClientEncoding.
So, I broke this last week by moving GUC processing to after InitPostgres :-(.
What we can do as a compromise is process non-SUSET variables during
command line scanning (the same as before), and postpone the processing
of only SUSET variables.  None of the SUSET variables need to be set
before InitPostgres.

Per report from Mark Kirkwood.

include "\s" in \? output when readline is enabled, but that commit
supressed "\s" whether readline was enabled or not.

a home-brewed combination of assertions that boiled down to the same
thing.