Log Message:
---
Improve efficiency of attribute scanning in CopyReadAttributesCSV.
The loop is split into two parts, inside quotes, and outside quotes, saving
some instructions in both parts.
Heikki Linnakangas
Modified Files:
--
pgsql/src/backend/commands:
copy.
Log Message:
---
Improve pglz_decompress() so that it cannot clobber memory beyond the
available output buffer when presented with corrupt input. Some testing
suggests that this slows the decompression loop about 1%, which seems an
acceptable price to pay for more robustness. (Curiously,
[EMAIL PROTECTED] (Teodor Sigaev) writes:
> Fix memory arrangement of tsquery after removing stop words. It causes
> a unused memory holes in tsquery.
The buildfarm indicates there's something wrong with the 8.3 version
of this patch ...
regards, tom lane
--
Sent via pg
Log Message:
---
This patch addresses some issues in TOAST compression strategy that
were discussed last year, but we felt it was too late in the 8.3 cycle to
change the code immediately. Specifically, the patch:
* Reduces the minimum datum size to be considered for compression from
256 t
Log Message:
---
Add:
>
> * Add a function like pg_get_indexdef() that report more detailed index
> information
>
> http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php
>
Modified Files:
--
pgsql/doc:
TODO (r1.2281 -> r1.2282)
(http://anonc
Log Message:
---
Add:
>
>
> o Prevent autovacuum from running if an old transaction is still
> running from the last vacuum
>
> http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php
>
Modified Files:
--
pgsql/doc:
TODO (r1.2280
Log Message:
---
Added to TODO:
>
> * Allow text search dictionary to filter out only stop words
>
> http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php
Modified Files:
--
pgsql/doc:
TODO (r1.2279 -> r1.2280)
(http://anoncvs.postgresql.or
Log Message:
---
Add to TODO:
>
> * Consider allowing higher priority queries to have referenced buffer
> cache pages stay in memory longer
>
> http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php
Modified Files:
--
pgsql/doc:
TODO (r1.2278 -> r1
Log Message:
---
Add:
>
> * Improve referential integrity checks
>
> http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php
Modified Files:
--
pgsql/doc:
TODO (r1.2277 -> r1.2278)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?
Log Message:
---
Add item:
> o Store per-table autovacuum settings in pg_class.reloptions.
>
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg01440.php
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00724.php
Modified Files:
--
pg
Log Message:
---
Add URL for:
* Allow multiple identical NOTIFY events to always be communicated to the
client, rather than sent as a single notification to the listener
http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
Modified Files:
--
pgsql/doc:
Log Message:
---
Add:
> o Add SQLSTATE severity to PGconn return status
>
> http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php
Modified Files:
--
pgsql/doc:
TODO (r1.2274 -> r1.2275)
(http://anoncvs.postgresql.org/cvsweb.cg
Log Message:
---
Change hashscan.c to keep its list of active hash index scans in
TopMemoryContext, rather than scattered through executor per-query contexts.
This poses no danger of memory leak since the ResourceOwner mechanism
guarantees release of no-longer-needed items. It is needed be
Log Message:
---
Change hashscan.c to keep its list of active hash index scans in
TopMemoryContext, rather than scattered through executor per-query contexts.
This poses no danger of memory leak since the ResourceOwner mechanism
guarantees release of no-longer-needed items. It is needed be
Log Message:
---
Change hashscan.c to keep its list of active hash index scans in
TopMemoryContext, rather than scattered through executor per-query contexts.
This poses no danger of memory leak since the ResourceOwner mechanism
guarantees release of no-longer-needed items. It is needed be
Log Message:
---
Change hashscan.c to keep its list of active hash index scans in
TopMemoryContext, rather than scattered through executor per-query contexts.
This poses no danger of memory leak since the ResourceOwner mechanism
guarantees release of no-longer-needed items. It is needed be
Log Message:
---
Change hashscan.c to keep its list of active hash index scans in
TopMemoryContext, rather than scattered through executor per-query contexts.
This poses no danger of memory leak since the ResourceOwner mechanism
guarantees release of no-longer-needed items. It is needed be
Log Message:
---
Add:
> o Have \l+ show database size, if permissions allow
>
> Ideally it will not generate an error for invalid permissions
>
Modified Files:
--
pgsql/doc:
TODO (r1.2273 -> r1.2274)
(http://anoncvs.postgresql.org/cvsweb.cgi
Log Message:
---
Fix memory arrangement of tsquery after removing stop words. It causes
a unused memory holes in tsquery.
Per report by Richard Huxton <[EMAIL PROTECTED]>.
It was working well because in fact tsquery->size is not used for any
kind of operation except comparing tsqueries.
Log Message:
---
Add:
>
> * Add comments on system tables/columns using the information in
> catalogs.sgml
>
> Ideally the information would be pulled from the SGML file
> automatically.
>
Modified Files:
--
pgsql/doc:
TODO (r1.2272 -> r1.2273)
(ht
Log Message:
---
Fix memory arrangement of tsquery after removing stop words. It causes
a unused memory holes in tsquery.
Per report by Richard Huxton <[EMAIL PROTECTED]>.
It was working well because in fact tsquery->size is not used for any
kind of operation except comparing tsqueries.
21 matches
Mail list logo
