from the pg doc:
http://www.postgresql.org/docs/devel/static/wal-reliability.html :On Linux,
IDE drives can be queried using hdparm -I; write caching is enabled if
there is a * next to Write cache. hdparm -W 0 can be used to turn off write
caching. SCSI drives can be queried using
On Sat, Apr 6, 2013 at 1:36 PM, Jeff Janes jeff.ja...@gmail.com wrote:
On Fri, Apr 5, 2013 at 6:09 AM, Andres Freund and...@2ndquadrant.com
wrote:
How does the attached version look? I verified that it survives
recovery, but not more.
Jeff, any chance you can run this for a round with your
On 04/07/2013 02:29 PM, Jov wrote:
from the pg doc:
http://www.postgresql.org/docs/devel/static/wal-reliability.html :On Linux,
IDE drives can be queried using hdparm -I; write caching is enabled if
there is a * next to Write cache. hdparm -W 0 can be used to turn off
write caching. SCSI
While reviewing the latest incarnation of the regex indexing patch,
I noticed that make_trigrams() in contrib/pg_trgm/trgm_op.c is coded
so that if USE_WIDE_UPPER_LOWER is not set, it ignores multibyte
character boundaries and just makes trigrams from 3-byte substrings.
This seems slightly insane,
Jeff Janes escribió:
Is this functionality something we want? If so should it include explicit
vacuum as well as autovac?
Yes. No.
Any opinion about where in the code base it
properly belongs (which obviously depends on whether it should cover manual
vacuum as well)? And does the string
On Sun, Apr 7, 2013 at 7:43 PM, Tom Lane t...@sss.pgh.pa.us wrote:
While reviewing the latest incarnation of the regex indexing patch,
I noticed that make_trigrams() in contrib/pg_trgm/trgm_op.c is coded
so that if USE_WIDE_UPPER_LOWER is not set, it ignores multibyte
character boundaries and
Alexander Korotkov aekorot...@gmail.com writes:
It's also likely we can change
if (pg_database_encoding_max_length() 1)
into something like
if (pg_database_encoding_max_length() 1 bytelen != charlen)
Hm, actually couldn't we just simplify to if (bytelen != charlen)?
On Sun, Apr 7, 2013 at 10:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alexander Korotkov aekorot...@gmail.com writes:
It's also likely we can change
if (pg_database_encoding_max_length() 1)
into something like
if (pg_database_encoding_max_length() 1 bytelen != charlen)
Hm,
Alexander Korotkov aekorot...@gmail.com writes:
On Sun, Apr 7, 2013 at 10:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Hm, actually couldn't we just simplify to if (bytelen != charlen)?
I think yes, we can :)
OK. I pushed this as a separate commit so as to highlight the potential
Hello,
While going through the TODO items on the wiki I have come across the
following proposal:
Provide a way to query the log collector subprocess to determine the
name of the currently active log file
Current log files when rotating?
On 6.4.2013 21:51, Tomas Vondra wrote:
Hi,
I'm regularly using pg_stat_database view to analyze various aspects of
behavior of the cluster. The #1 issue I'm constantly running into is
that to get cluster-level view (across all the databases), the table
needs to be aggregated like this:
Hi,
I'm learning how to use the background worker processes commited in
9.3. The usage basics are quite nicely illustrated in the worker_spi
extension (kudos to those who designed the feature / extension).
I'm not quite sure how to pass data between the regular backend and a
worker. Implementing
Hi,
Far as I am aware - there is not yet described FK feature...
But should be possible to ensure that rule via trigger.. 1 after update on
container, and one after insert/update on item...
Kind Regards,
Misa
On Saturday, April 6, 2013, Matthias Nagel wrote:
Hello,
this is a re-post from
On 7 April 2013 01:43, Kevin Grittner kgri...@ymail.com wrote:
Brendan Jurd dire...@gmail.com wrote:
Indeed it does not prohibit nesting arrays inside other arrays, but
the multidim arrays that Postgres allows you to create are not the
same thing as nested arrays.
Your interpretation matches
Alexander Korotkov aekorot...@gmail.com writes:
[ trgm-regexp-0.15.patch.gz ]
I spent the weekend hacking on this, making a number of bug fixes and a
whole lot of cosmetic changes. I think there are large parts of this
that are in committable shape now, but I still find the actual graph
15 matches
Mail list logo