13869'::regclass;
>
> oid | pg_temp_24.tmp_isp_blk_chk
The regular table had not shown up on a query of age(relfrozenxid) WHERE
relkind='r' but the toast table showed up on a similar query with WHERE
relkind='t'.
--
Andrew, Supernews
http://www.supernews.co
design) true in UTF8, but is not true of most other
multibyte charsets.
The %_ case is also trivially handled in UTF8 by simply ensuring that
_ doesn't match a non-initial octet. This allows % to advance by bytes
without danger of losing sync.
--
Andrew, Supernews
http://www.supernews
on whether it will be
followed by listen() or connect(); this was not well understood by the
original designers of the API, hence the use of SO_REUSEADDR as a klugy
way of saying "I'm going to use listen() on this socket after the bind".)
--
Andrew, Supernews
http://www.supernews.com
his is a problem in FreeBSD, not specifically to do with postgres - the
granularity for SysV semaphore wakeups in FreeBSD-6.x and earlier is the
entire semaphore set, not just one specific semaphore within the set. I
explained that to Kris some weeks ago, and someone (mux) did a patch (to
FreeBSD,
On 2007-04-05, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
>> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> > Thinking about this made me realize that there's another, ahem, elephant
>> > in the room here: convert().
>> > By definition convert
; point, converted to the local client_encoding per conversion_procs.
Thinking about this made me realize that there's another, ahem, elephant
in the room here: convert().
By definition convert() returns text strings which are not valid in the
server encoding. How can this be addressed?
sequences of
_bytes_ that represent that code point in various encodings, of which the
three-byte sequence 0xE2 0x82 0xAC is the one used in UTF-8.
Functions like chr() and ascii() should be dealing with the _number_ of the
code point, not with its representation in transfer encodings.
--
A
n setting to use.
Treating the parameter as bytes is wrong too - it should correspond to
whatever the natural character numbering for the encoding is; for utf8
that is the Unicode code point.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
-
these functions in this regard?
The chr() function returns an octet, rather than a character; this is clearly
wrong and needs fixing.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
T
_create_with_catalog in backend/catalog/heap.c.
You've still got the usage of the relation OID and the relation _type_ OID
reversed.
The array element type that you pass to TypeCreate must be the _type_ OID.
--
Andrew, Supernews
http://www.supernews.com - individual
goal_ of UTF8. Treating UTF8 like any other multibyte charset and
converting everything to wide-chars is, in my opinion, always going to
result in suboptimal performance.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of
wo two-octet characters AB, the second octet of A plus the first octet
of B is not a valid UTF8 character (and likewise for longer characters).
(And while I haven't tested it, it looks like the patch posted doesn't
account properly for the use of _, so it needs a bit more work.)
hat came from a tuple,
but from data that came from a decompress method. It's expected that the
decompress method does the detoasting.
So I think you've mis-analyzed the problem. That's especially true since
you are claiming that the existing code is already buggy when in fact
On 2007-03-04, William ZHANG <[EMAIL PROTECTED]> wrote:
> Here is the steps to reproduce it in CVS HEAD:
> backend> select -1 !=-1;
This arguably isn't a bug, because != is not a standard SQL operator, and
therefore !=- can legitimately be defined as a single operator by t
On 2007-03-02, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2007-03-02, Gregory Stark <[EMAIL PROTECTED]> wrote:
>>> I think these are actual bugs. If you happened to provide a large enough
>>> datum
>>
nto account the fact that, at least prior to your patch,
values in index tuples could never be toasted?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
reason I've not done another release
yet is because I haven't had a chance to test for regressions on 8.1.
--
Andrew, Supernews
http://www.supernews.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On 2006-12-13, "Simon Riggs" <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-12-13 at 19:28 +, Simon Riggs wrote:
>> On Wed, 2006-12-13 at 04:23 +, Andrew - Supernews wrote:
>> > While testing a PITR recovery, I discovered that recovery.conf doesn't
>>
On 2006-12-13, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2006-12-13, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> BTW, I think it's possible to prove that there need never be two for the
>>> case of both
ique join operator due to
trichotomy, but this is not true for the sortops. While the above is
a bit contrived, I think non-contrived examples could be found too.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)-
allows \' (e.g. archive_command = '/path/to/script \'%f\' \'%p\'').
Should this be fixed?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 3: Have y
tus" column on a row, do I have two copies of "big_text" TOASTED
> or are they shared?
Shared.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On 2006-09-23, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> Whether the underlying device lies about the write completion is another
>> matter. All current SCSI disks have WCE enabled by default, which means
>> that they w
FreeBSD, this command will disable WCE permanently on a SCSI drive:
echo 'WCE: 0' | camcontrol modepage daXX -m 8 -P3 -e
(use -P0 to disable it only temporarily, or you can use just the second of
those commands alone to interactively edit the mode page)
--
Andrew, Supernews
http
can never know) that no-one else is using the same
MAC address. Anyone with substantial experience in networking will tell
you that the supposed "uniqueness" of manufacturer-assigned MACs is often
a myth, with (in extreme cases) entire batches of NICs being manufactured
with the same
On 2006-09-18, James William Pye <[EMAIL PROTECTED]> wrote:
> FWIW, I'm +1 on the cleaner design you suggested. While I understand the
> concerns of adding features/API this late;
Adding features is one thing, breaking existing users of the code is another.
--
Andre
it just doesn't list aliases (which
it isn't supposed to). The reason to include zone.tab in with the data
(unlike the current setup which doesn't bother to even install the file
anywhere) is to provide an answer to the question "what timezone(s) are
applicable to a specific cou
On 2006-09-15, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews wrote:
>> Numbers from an actual benchmark:
>>
>> int4out(0) - 0.42us/call
>> numeric_out(0) - 0.32us/call
>>
>> int4out(10) - 0.67us/call
>> numer
enerate_series(1,1000) s2;
This calls int4out(0) a million times. (the input function is only called
once since it is a constant, and therefore handled during planning)
select 0::numeric from generate_series(1,1000) s1,
generate_series(1,1000) s2;
This calls numeric_out(0) a
On 2006-09-15, "D'Arcy J.M. Cain" wrote:
> On Fri, 15 Sep 2006 10:17:55 -
> Andrew - Supernews <[EMAIL PROTECTED]> wrote:
>> Presumably the same speed as bigint, which is to say that while it is
>> faster than numeric for calculation, it is (much) slow
bad query plans for later commands in the transaction.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscri
ric output is
measured in multiples, not in percentages.)
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose
ys.
You're confusing locale and charset.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
fact
> there's no need for it to take more than 87 bytes.
Are you sure? Perhaps you are assuming that a char(1) field can be made
to be fixed-length; this is not the case (consider utf-8 for example).
--
Andrew, Supernews
http://www.supernews.com - individual a
ink the existing view
> is wrongly named --- perhaps it should be pg_timezoneabbrevs? Or
> more readably, perhaps pg_timezone_abbrevs, with pg_timezone_names for
> the other view.
Yes, the abbreviations table is definitely misnamed.
--
Andrew, Supernews
http://www.supernews.com - individual
nal discussion (which was a
year and a half or so ago). However, others seemed to disagree, which is
why we now have a replacement version.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)--
meone will do the legwork to define and implement them.
So you're prepared to violate the feature freeze to stick in a new API
that nobody currently wants to _use_, while forcing existing users to
resort to pgfoundry for a module that's been around for several major
releases?
--
Andr
On 2006-09-05, "Merlin Moncure" <[EMAIL PROTECTED]> wrote:
> On 9/5/06, Andrew - Supernews <[EMAIL PROTECTED]> wrote:
>> On 2006-09-05, Josh Berkus wrote:
>> > The current code is GPL. It *has* to be removed.
>>
>> Which is why Abhijit'
On 2006-09-05, Josh Berkus wrote:
> The current code is GPL. It *has* to be removed.
Which is why Abhijit's version exists - it's intended to be a drop-in,
BSD-licensed replacement for the current code.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate
mode as a magic number isn't ideal.
> And then there's the question of what to expose in the way of lock
> identifier options. What we've got now is "two int4's or an OID"
> which seems a bit random, not to mention that the key space overlaps
> in an u
ps he would be prepared to turn that into a patch against the core...
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desi
uce a plan that was
equivalent to that of a non-parameterized query.
This would hopefully remove all cases where it is currently necessary to
use PQexec rather than PQexecParams, such as where parameterized limits,
immutable functions of parameters, partial indexes etc. are involved.
--
Andrew,
< y "x is strictly contained in y"
(obviously these don't all necessarily make sense for all types)
These have the advantage of resembling set notation more closely and being
in use in one existing core type.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 6: explain analyze is your friend
those are the only two places where preparation is the default
RI triggers.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an
easonably as the scale is
> different.
The comparison function must be trichotomous, that is the possible results
are "equal", "greater", and "less". There is no other "not equal" result.
--
Andrew, Supernews
http://www.supernews.com - individual and corpor
le, when the
executor already has that functionality built in?).
Here's your brute-force password crack (try it! should only take an hour or
two) using the simple alpha(n) function example from my other post:
select a||b||c from alpha(3) s1(a), alpha(3) s2(b), alpha(2) s3(c)
where md5(
t noticed before he's succeeded.
> (And certainly, doing anything compute-intensive via recursive SQL
> functions is not the way to go unnoticed.)
Doing something compute-intensive with pl/pgsql functions will be just as
noticable.
--
Andrew, Supernews
htt
On 2006-04-11, Richard Huxton wrote:
> Andrew - Supernews wrote:
>> On 2006-04-11, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> I don't feel a need to offer specific examples as requested by Andrew.
>>
>> Why not? You're basing your entire argumen
y certainty.
pl/pgsql is not comparable to other PLs in this case. Specifically, it
does not provide access to any functionality that is not already part of
Postgres itself.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On 2006-04-11, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2006-04-10, Bruce Momjian wrote:
>>>> [ security ]
>>> It actually is the reason I have heard.
>
>> And it was duly debunked.
>
> Th
>
> It actually is the reason I have heard.
And it was duly debunked.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
mit; that means that it can't allow concurrent
access to the table since it is going to delete old tuples that might
otherwise still be visible to other transactions. DELETE on the other hand
simply marks the old tuples as dead; remember to vacuum as needed to clean
up.)
--
Andrew, Supernews
h
> held throughout the entire SP, not just during the execution of the
> TRUNCATE command. Shouldn't TRUNCATE be releasing the lock as soon as
> it finishes?
No, locks are always held until the end of the transaction.
--
Andrew, Supernews
http://www.supernews.com - ind
On 2006-03-02, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> No. Here is the offending SP:
>
> CREATE OR REPLACE FUNCTION update_my_cache() RETURNS void AS '
> BEGIN
>
> TRUNCATE TABLE my_cache_table;
TRUNCATE is another command that takes an access exclusive lock
of one or more s.
b. Otherwise, if FS is any other character c, fields shall be
delimited by each single occurrence of c.
3. Otherwise, the string value of FS shall be considered to be an
extended regular expression. Each occurrence of a sequence
matching the ext
ybe?) where they'd pose less risk of conflicts with user-defined names.
> Does newsysviews already do this?
The current version in pgfoundry CVS uses "pg_sysviews" as the schema name.
If you have any better suggestions for the name, or any other aspect of the
projec
ght in such cases (which I would
strongly favour), it is likely that there will always be ways to get
malformed sequences into the backend (which itself is far too lax
about parsing them).
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---
On 2006-02-20, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
> In further investigation, Akio Ishida found this kind of attack is
> possible even with EUC_JP/UTF-8.
How?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
--
here you'd expect. This seems to be
something to do with the fact that it's not pg_authid which is being
accessed, but rather the view pg_roles.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
ower input set
than that accepted by inet_aton().
The spec is quite explicit that inet_pton is not expected to accept the
abbreviated forms or any non-decimal values.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of br
due to the need to support ipv6.
If you want that for ip4-only apps, that's why pgfoundry.org/projects/ip4r
exists. It is possible that ip4r will be extended to ipv6 addresses, but
most unlikely that it will ever implement the overloaded "inet" semantics.
--
Andrew, Supernews
but
> what other default netmask would you suggest anyways?
The one implied by the number of octets specified, assuming you are going
to accept the abbreviated forms at all.
(FWIW, ip4r at this time does not even accept '10.1/16', it insists on
'10.1.0.0/16'.)
On 2006-01-25, Bruce Momjian wrote:
> Andrew - Supernews wrote:
>> Having the behaviour be dependent on which part of the IP space is used
>> is a total nonsense on the modern, CIDR, internet! The C in CIDR even
>> stands for "Classless", so how can you ever ju
f the IP space is used
is a total nonsense on the modern, CIDR, internet! The C in CIDR even
stands for "Classless", so how can you ever justify introducing _new_,
non-traditional, dependencies on the traditional classes?
--
Andrew, Supernews
http://www.supernews.com - individual and c
t like the relation
> between varchar and text. For instance, varchar doesn't have any
> comparison operators of its own, but piggybacks on text's comparison
> operators, relying on the implicit cast from varchar to text to make this
> transparent to users.
Well, inet/cidr h
in questions asked on the IRC channel), and the problem can't be
worked around at the application level without knowing the value of
MAX_RANDOM_VALUE in order to correct the range to [0.0,1.0).
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP ser
it must be a strict weak ordering
for sorting to even work, and such an ordering is completely determined by
either one of its greater-than/less-than operators?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast
olumn sort of the following data:
('Foo',1)
('foo',2)
('Foo',3)
would produce the wrong output, no?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
table < operator, i.e. one that constitutes a strict weak
ordering over the elements to be sorted; it can rely on the fact that
NOT(a < b) AND NOT(b < a) implies that a and b are equivalent for sorting
purposes. (The requirement that < constitute a strict weak ordering is
enough to ensur
that a share lock is requested(and hold) on each of them once
> one is dumped, i.e., sequentially?
pg_dump obtains an ACCESS SHARE lock on _every_ table it dumps, including
the inherited child tables individually, _before_ it starts dumping anything.
--
Andrew, Supernews
http://www.supernews.co
AccessShare locks block behind the pending AccessExclusive lock.
Otherwise AccessShare locks could starve the exclusive lock forever.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP
res UTF-16 for
> everything.
Even UTF-16 is not fixed-length; some characters require 4 bytes, not 2.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 3: Have you checked our exte
e 8.1 database (unless the admin did that
explicitly, themselves).
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On 2005-10-27, Paul Lindner <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 24, 2005 at 05:07:40AM -0000, Andrew - Supernews wrote:
>> I'm inclined to suspect that the whole sequence c1 f9 d4 c2 d0 c7 d2 b9
>> was never actually a valid utf-8 string, and that the d2 b9 is on
On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> Pretending it's the user's mistake isn't
>>> an answer that fits down my craw ve
On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> Uh, no ... the global setting of add_missing_from does *not* tell you
>>> anything about whethe
On 2005-10-26, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> Wild idea: how about having pg_dump include SET add_missing_from = true;
>> in the dump file if, and only if, it is set that way in the server?
>
>
in the dump file if, and only if, it is set that way in the server?
Perhaps do this only for server versions <8.1... and ensure that dumps
from an 8.1 server include the explicit table names...
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
Azerbaijani). I know the 8.0
utf-8 check was broken, but I didn't realize it was quite so bad.
> and
>
> B7 ED A8
Likewise, that whole sequence b7 ed a8 c6 a4 was probably never valid;
c6 a4 also isn't a character you'd expect to find in common use.
My guess is that this wa
Does the 8.1 Unicode sanity code accept the full set of characters
> accepted by the 8.0 Unicode sanity code?
No. 8.0 and before accepted a lot of stuff that it should never have, and
failed to accept stuff that it should have.
--
Andrew, Supernews
http://www.supernews.com - ind
If he's using bytea columns, then he doesn't want that.
Most likely the interface he's using is assuming lo_* style blobs, rather
than bytea.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)
. pclose() is not a
signal-safe function, so it can only be called from a signal handler if
you _know_ that the signal did not interrupt any non-signal-safe function.
(Nor can the signal handler longjmp out in such a case, unless the code is
never again going to call any unsafe function.)
--
I do a schema-only dump of that table? I find that I need
> SELECT permission on the table, even though my user can happily query
> the catalogs.
pg_dump takes an access share lock on everything it touches, to avoid
having the schema change out from under it.
--
Andrew, Supernews
http://ww
On 2005-10-12, Andrew - Supernews <[EMAIL PROTECTED]> wrote:
> On 2005-10-12, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>>> As the number of items in the IN clause increases, the planning time grows
>>>
On 2005-10-12, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> As the number of items in the IN clause increases, the planning time grows
>> rather radically.
>
> I was looking at this yesterday. There is some O(N^2) be
epare in advance every
possible number of parameters to IN that your app is ever going to use,
the only way to get useful performance for IN queries with more than a
handful of literal values is to use an array method, in spite of the fact
that the bitmap-OR execution plan is actually at leas
On 2005-09-08, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews wrote:
>> On 2005-09-08, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
>> > Andrew - Supernews wrote:
>> >> Running initdb behind the scenes is a proven dangerous practice
On 2005-09-08, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews wrote:
>> Running initdb behind the scenes is a proven dangerous practice
>
> Please elaborate.
Example instance:
http://archives.postgresql.org/pgsql-hackers/2004-12/msg00851.php
More genera
emove options from initdb, not add them.
Running initdb behind the scenes is a proven dangerous practice; why
encourage it?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 9: In versi
ect '192.168.0.1/24'::inet + -1;
> ERROR: Increment returns a network (192.168.0.0/24) rather than a host
While I suspect I know where this idea came from, it is equally boneheaded
since it is making completely unwarranted assumptions about how inet
values are being used.
--
Andrew, Sup
27; databases.
Which implies either that you limit each dbowner to one db (in which case
why give them createdb privilege in the first place) or that you require
superuser intervention to modify pg_hba for each database created.
--
Andrew, Supernews
http://www.supernews.com - individual and corpora
On 2005-09-01, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2005-09-01, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> Change the ownership of public in template1 to be a "dbadmin" group.
>>> Grant member
On 2005-09-01, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2005-09-01, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> There is some merit in the thought that the DB owner should be able to
>>> grant and revoke ac
On 2005-09-01, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> On 2005-09-01, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> There's considerable feeling that that TODO item is bogus anyway.
>
>> The issue that I&
le, why
> run vacuum at all? You can (as of 8.1) disable autovacuum for specific
> tables. The exception is that you are forced to run a database-wide
> VACUUM once in a while (every billion-and-so), but this will hopefully
> disappear in 8.2 too,
Wishful thinking, or do you
_ than public.)
(Another wart that could do with looking into is that such a non-superuser
database owner can't prevent xid wrap in his database regardless of how
often he vacuums it.)
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
is read in SnapshotNow rather than in the query
snapshot.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 6: explain analyze is your friend
ger type, or even a scalar type; it's permitted to
be a structure. The only valid operations on pthread_t values are assignment
and passing to functions (including pthread_equal() for equality comparison).
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
o page caching, so shared_buffers should be increased to
> account for this fact.
>
> Am I missing something?
O_DIRECT should only be being used for the WAL, not for buffer I/O.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
-
push
> oid to 4 billion.
Don't forget TOAST tables, they use oids too.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 4: Have you searched our list archive
1 - 100 of 166 matches
Mail list logo
