names...
+1
BTW, if people want to get anal with the names I think it's fine to
also have options to explicitly name the files, but for normal usage
I'd much rather have a simple option flag that just appends stuff to
--file.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL
On Feb 9, 2008, at 1:08 AM, Tom Lane wrote:
Let's not swat flies with steam hammers.
What the heck is a steam hammer? :P
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S
additional shm segments?
>
> Sounds possible.
If we build that, it's probably not a far stretch to just allocate
shared memory as a number of smaller segments; that would allow us to
grow as well as shrink.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
a large schema we might rather want one switch that dumps 2 files,
> no ?
> Probably also better from a mvcc perspective.
+1
For that matter, it'd be better if you could just get all 3 files (pre,
data, post) in one shot with one transaction; that would guarantee you a
clean dump.
On Tue, Feb 05, 2008 at 01:54:17PM -0800, Ron Mayer wrote:
> Decibel! wrote:
> >
> > Yes, this problem goes way beyond OOM. Just try and configure
> > work_memory aggressively on a server that might see 50 database
> > connections, and do it in such a way that you won&#
e really do need a way to limit how much memory we will use in total.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
pgp4bgwyT7x7v.pgp
Description: PGP signature
On Thu, Jan 31, 2008 at 11:45:55AM +, Simon Riggs wrote:
> On Thu, 2008-01-31 at 10:22 +, Gregory Stark wrote:
> > "Decibel!" <[EMAIL PROTECTED]> writes:
> >
> > > CLUSTER isn't DDL. Most forms of ALTER TABLE are. And CREATE blah, etc.
> &g
care about how
long analyze takes, though perhaps it should have a throttle ala
vacuum_cost_delay.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
pgpbkSuadbMUY.pgp
Description: PGP signature
On Mon, Jan 28, 2008 at 09:09:13PM -0300, Alvaro Herrera wrote:
> Decibel! wrote:
> > On Fri, Jan 25, 2008 at 11:40:19AM +, Simon Riggs wrote:
> > > (for 8.4 ...)
> > > I'd like to introduce triggers that fire when we issue a truncate:
> >
> > Rathe
On Mon, Jan 28, 2008 at 11:14:05PM +, Christopher Browne wrote:
> On Dec 6, 2007 6:28 PM, Decibel! <[EMAIL PROTECTED]> wrote:
> > FWIW, I've never seen anything but a performance increase or no change
> > when going from 10 to 100. In most cases there's a notice
I had a mail issue on my end which resulted in a number of outbound
emails getting stuck in a queue. They all just went out; sorry for the
flood.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
ansactions; save the current
session to the stack, clone it, run the autonomous transaction, then
restore the saved one.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
pgpKD3eTOJmEA.pgp
Description: PGP signature
seen anything but a performance increase or no change
when going from 10 to 100. In most cases there's a noticeable
improvement since it's common to have over 100k rows in a table, and
there's just no way to capture any kind of a real picture of that with
only 10 buckets.
--
Deci
ded?
That would make it easier to protect against deadlocks...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
pgpEq5RUInVoR.pgp
Description: PGP signature
on't know about *requiring* this, but it would certainly be a nice
option to have. Right now there's absolutely no way that you could get
Postgres to use a port < 1024.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.dist
, when we're scanning
the index, we'd definitely want to issue heap page requests
asynchronously, since that gives the filesystem, etc a better shot at
re-ordering the reads to improve performance.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer som
truncate is
more DML than DDL, but still).
The reason I put triggers in quotes is because I'm not suggesting that
we actually put triggers on the catalog tables, since we all know that's
hard/impossible. Instead this would have to tie into command processing,
similar to what you're
I'd rather wait for 8.4 than put
#2 in...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
rofile
and couldn't find anything significant. Eventhough it shows 4391
physical reads, that's from OS cache, since i ave already run the
query multiple times.
Have you tried just executing the query with executor stats on? You
could be seeing the overhead of explain analyze...
r your attention and for your time.
Regards, Manolo.
_
Express yourself instantly with MSN Messenger! Download today it's
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---(en
nally? Also, testing on 64 bit would be interesting.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
this or
how to decide when to do it.
TODO?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
ther doubt that we're the only userland
software that would make use of that.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
onsidering NUMA architecture. *comes-
to-think-again*...
Except that doing something in-machine is often far simpler than
trying to go cross-machine, especially when that something is a
background reader.
Let's walk before we run. :)
--
Decibel!, aka Jim C. Nasby, Database Architect [E
ield sizes.)
I've wanted the ability to define different toast limits for a long
time (so for example you could say that any fields over 100 bytes get
toasted). I might be able to get sponsorship for this, if others are
interested enough to pony up $$ please contact me.
--
Decibel!, a
at
would actually tell us if the kernel issued physical IO? I find it
hard to believe that other RDBMSes wouldn't like to have that info...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7
e requests to the drive. Doing
so allows the drive to optimally order all of the reads.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
On Dec 4, 2007, at 4:48 PM, Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Dec 2007 16:41:52 -0600
Decibel! <[EMAIL PROTECTED]> wrote:
On Nov 15, 2007, at 4:41 AM, Gregory Stark wrote:
Ask me about EnterpriseDB's Slony Replication support!
On Nov 15, 2007, at 4:41 AM, Gregory Stark wrote:
Ask me about EnterpriseDB's Slony Replication support!
Hah, wtf is that all about? :)
BTW, looked at londiste?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distribute
On Nov 2, 2007, at 10:49 AM, Andrew Dunstan wrote:
update tname set foo = bar ... where foo is null or foo <> bar ...
FYI, you should be able to do WHERE foo IS DISTINCT FROM bar instead.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some
s, but it would be very nice if you could just do
$blah in embedded SQL statements.
While we're talking about plpgsql... is there a TODO to allow RAISE
to take a variable instead of just a fixed string? Yes, I can always
do RAISE '%', variable, but then I lose % expansion.
On Nov 2, 2007, at 11:29 AM, Tom Lane wrote:
[ splorfff... ] The grammar support alone will cost ten times that.
When next we meet, expect me to ask you how that's pronounced. ;)
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain
On Oct 18, 2007, at 11:17 PM, Joe Conway wrote:
Decibel! wrote:
Is it intentional that dblink's unnamed connections don't get re-
used?
yes
stats=# select dblink_connect('dbname=stats');
dblink_connect
OK
(1 row)
stats=# select dblink_conn
where people had set this to a very high value under
the impression that it impacted prepared statements.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
---(end of broadcast)--
Sorry for the self-reply...
On Oct 18, 2007, at 9:09 AM, Decibel! wrote:
Is it intentional that dblink's unnamed connections don't get re-used?
From the dblink docs (both 8.1 and HEAD):
if only one argument is given, the connection is unnamed; only
one unnamed
connection
Is it intentional that dblink's unnamed connections don't get re-used?
stats=# select datname, usename from pg_stat_activity;
datname | usename
-+-
stats | decibel
(1 row)
stats=# select dblink_connect('dbname=stats');
dblink_connect
OK
(1
On Tue, Oct 02, 2007 at 09:07:54PM -0400, Alvaro Herrera wrote:
> Decibel! wrote:
>
> > Hrm... what about adding output to vacuum verbose that indicates how many
> > pages in a relation have free space? That would allow something like
> > pgfouine to see how many FSM pag
w something like
average free space per page).
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
---(end of broadcast)---
TIP 3: Have you check
On Sep 19, 2007, at 2:08 AM, Guillaume Smet wrote:
On 9/19/07, Decibel! <[EMAIL PROTECTED]> wrote:
Odd... I'd expect it to actually be beneficial to run analyze on a
table
at roughly the same time as PK building, because you'd make better
use
of cache.
Sure if your databa
On Sep 19, 2007, at 8:08 AM, Tom Lane wrote:
Decibel! <[EMAIL PROTECTED]> writes:
3 isn't that important to me, but 4 is:
4. Doesn't hammer the database to measure
And pgstattuple fails #4 miserably. Want to know the average dead
space
in a 500GB database? Yeah, right
ess something's changed, analyze should read at most
30k pages, which I wouldn't expect to take all that long...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
pgpjuvHWopLgw.pgp
Description: PGP signature
As a DBA, I can say it doesn't really matter to me *how we track* the
> dead space, as long as tracking it is:
>
> 1. Clear
> 2. Simple
> 3. Available by default (thus pgstattuple needs to push into core)
3 isn't that important to me, but 4 is:
4. Doesn't hammer the d
least the first update (if not many more) to be
COLD.
I realize that ideally we'd probably want FILLFACTOR to take things like
average tuple size and average number of updates per page into account,
but for a first pass 90% would likely be a good compromise...
--
Decibel!, aka Jim C. Nasby, Dat
i will
> > let you know this
>
> Is this "apoc9009" guy real ?
Pretty much as soon as I saw that comment I just nuked the whole thread
and moved on. I suggest everyone else just do the same.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB
part of the little mini-transaction writes to the same
> "offset" (ie. each column in the record will have the same "hole", so
> when you go to write the record out, write it to the same "record
> spot"). This is where the control column not only coordinates deletes
> but also inserts that re-use space from deleted records.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgp0bviTEQ2r6.pgp
Description: PGP signature
On Wed, Sep 05, 2007 at 03:27:50PM -0400, Tom Lane wrote:
> Decibel! <[EMAIL PROTECTED]> writes:
> > While this is correct on a per-relation level, I'm thinking that it's
> > not what we'd really like to have happen in psql. What I'd like \d to do
> >
can be hard-coded like that. What if checkpoint_timeout is set to 120?
Or 60? Or 2000?
I don't know that there should be a direct correlation, but ISTM that
scan_whole_pool_seconds should take checkpoint intervals into account
somehow.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpiBGkQouND3.pgp
Description: PGP signature
ing in any schema that's in my search_path, even if
there's something higher in the search_path that would over-ride it.
ISTM that's what most people would expect out of \d.
If no one objects I'll come up with a patch for this.
--
Decibel!, aka Jim Nasby[EMAIL PR
ld?
I wrote some code that does this back when I was thinking about writing
a book, if anyone wants to see it.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpfIY6tWUOJ1.pgp
Description: PGP signature
On Sun, Sep 02, 2007 at 11:18:45PM -0300, Marc G. Fournier wrote:
> Should be fixed now, running a manual run of it right now, give it about 15
> minutes or so ...
Is there now monitoring for it as well?
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB
, transaction-level, and sub-transaction level. If we had
that, we could probably make an across-the-board call that all functions
operate as if in their own sub-transaction, at least when it comes to
SET.
Whatever we decide on, least-surprise would dictate that it's the
same whether you apply
of GUCs on a function, having a load of SET
statements might be a bit tedious... I'm wondering if there's some way
to specify them like an array?
SET {'search_path=CURRENT', 'enable_seqscan=false', ...}
Or now that we have arrays of complex types, perhaps an array of t
On Fri, Aug 31, 2007 at 03:11:29PM -0400, Tom Lane wrote:
> Decibel! <[EMAIL PROTECTED]> writes:
> > Even if we don't care about folks running on suspect hardware, having a
> > CRC would make it far more reasonable to recommend full_page_writes=3Doff.
>
> This arg
asswords in a config file somewhere then?
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpXPYWPrJRvk.pgp
Description: PGP signature
s we discover how enums are used in practice.
Looks good... should still be a psql command, imo. Perhaps as part of
\dT...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpWfs9AG9Wy9.pgp
Description: PGP signature
On Fri, Aug 31, 2007 at 12:37:16PM -0400, Andrew Dunstan wrote:
>
>
> Decibel! wrote:
> >Is there something insecure about using ident sameuser for localhost
> >authentication on Windows?
> >
>
> FWIW, I never advise people to use ident auth for postgres excep
no way
> to list enum contents in psql (although you can list the enums
> themselves in the type listing). Maybe this should be possible? I'm
> willing to take a stab at these things if Andrew is busy.
Is there an SRF that will return this info? ISTM you should be able to
ge
er the page was
modified, instead of just when smgr went to write it out. How useful
that is I don't know...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpxszAG03fC9.pgp
Description: PGP signature
On Fri, Aug 31, 2007 at 09:02:49AM +0100, Dave Page wrote:
> Decibel! wrote:
> > Why does the windows installer require a password for the superuser
> > account, since it's perfectly legitimate not to have a password on that
> > account? I could see perhaps producing a
Why does the windows installer require a password for the superuser
account, since it's perfectly legitimate not to have a password on
that account? I could see perhaps producing a warning, but making
this a hard requirement seems like overkill.
--
Decibel!, aka Jim
... would there still be a README in each contrib directory?
I think getting this stuff in the docs is great, but the README in the
source is also very valuable and I'd hate to lose it.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpbJLvWh95Cg.pgp
Description: PGP signature
On Mon, Aug 27, 2007 at 11:59:05AM -0700, Joshua D. Drake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Decibel! wrote:
> > On Mon, Aug 27, 2007 at 08:08:34AM -0700, Joshua D. Drake wrote:
>
> >> This is a problem. Our analytics software purposefully
page so that you could "fix" the
corruption). Obviously, this should be restricted to superusers.
> At least you would know it was corrupted, instead of getting funky
> errors and/or crashes.
Or worse, getting what appears to be perfectly valid data, but isn't.
--
Decibel!, aka
nce
they have to stat each file, so I'm worried about what kind of load that
would present on a loaded system.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpcc6ArpkAWX.pgp
Description: PGP signature
ined to be really useful. If it was one bit
> per page it could work, but one bit per relation is going to be reset
> too frequently.
Not for the most common use cases for table partitioning.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpKGvmIPLYTD.pgp
Description: PGP signature
ook through the release notes... they go way back.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpTmJemIG86f.pgp
Description: PGP signature
ge to Bruce's idea is that it sounds pretty simple to
implement. While it wouldn't be of use for many general cases, it
*would* be useful for read-only tables, ie: old partitions.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://e
ill be read-only, which means there'd still be a lot of
benefit to simply using one transaction until the next write transaction
came along.
Something else to think about... any app that's doing that kind of
transaction rate is likely going to have a large number of backends, so
it would b
category = OLD.category;
> END IF;
> RETURN NEW;
> END
> $$ LANGUAGE plpgsql;
>
> CREATE TRIGGER actualise_cache
>AFTER INSERT OR UPDATE OR DELETE
>ON safecache.source_tbl
>FOR EACH ROW EXECUTE PROCEDURE safecache.source_tbl_trg_fce();
>
> ---(end
On Wed, Aug 15, 2007 at 06:47:05AM +0200, Pavel Stehule wrote:
> 2007/8/14, Decibel! <[EMAIL PROTECTED]>:
> > On Tue, Aug 14, 2007 at 05:38:33PM +0200, Pavel Stehule wrote:
> > > 2007/8/14, Bruce Momjian <[EMAIL PROTECTED]>:
> > > >
> > > >
day ToDo"?
> --
> "cbbrowne","@","acm.org"
> http://linuxfinances.info/info/postgresql.html
> "I don't do drugs anymore 'cause I find I get the same effect just by
> standing up really fast." -- Jonathan Katz
>
> -
oadcast)---
> > TIP 6: explain analyze is your friend
>
> I am against. It's too simple do it in SQL language.
Why make everyone who works with arrays create a function just to do
this? Something that's of use to common users should be included, simpl
spread all over creation in clear-text, even though it's entirely
possible for someone to connect to a running client with a debugger and
get a memory dump.
As I said before, I don't care what security you come up with, *it can
be broken*. The point of security me
straight noop alter table it's pretty trivial. The hardest part is coming up
> with a name for it.
One question... should we have a vacuum variant that also reindexes? Or
does that just naturally fall out of the rewrite?
BTW, rewrite sounds fine to me... anythin
w-car-prices for something
that's 5 years old...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpv9MZhCTRdP.pgp
Description: PGP signature
#x27;t know that there's much value in this...
> -compare data in indexes with indexed tables, whether they are correct
I think this should probably be top-priority, since the index code is
fairly complex this has a much higher likelyhood of bugs/problems.
--
Decibel!, aka Jim Nas
On Thu, Aug 09, 2007 at 11:41:02AM -0400, Andrew Dunstan wrote:
>
>
> Decibel! wrote:
> >This is also related to the desire to be able to restrict access to the
> >catalog tables. Doing so could potentially solve this problem; it
> >solves other issues (such a
ms.html
indicates that HPUX on PA-RISC should work...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpGfcyDpEN3F.pgp
Description: PGP signature
related to the desire to be able to restrict access to the
catalog tables. Doing so could potentially solve this problem; it also
solves other issues (such as being able to see all the databases that
exist on a server, something that hosting environments care about).
--
Decibel!, aka Jim Nasby
hooks as appropriate. That should
allow someone to develop the ability to encrypt the code in the database
outside of the backend.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpZN0BTyzThA.pgp
Description: PGP signature
to release this month, after all.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpkDxwB7dNwA.pgp
Description: PGP signature
y but
> the results don't then we might be doing a lot of work for nothing.
If we're going to get this into 8.3 I think we should be leaning towards
whatever is the simplest way to do it...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpPF8E4Vwj64.pgp
Description: PGP signature
s that we should have a way to convert arrays to sets
and back in the backend.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpbstK4UFlwR.pgp
Description: PGP signature
I might have missed something. Comments ?
ISTM if we add one for tables we should add one for indexes as well...
Or do we want different fill factors for different index methods?
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprise
If we wanted to get
fancy, perhaps we could track the amount of bloat in the heap as well as
the indexes, and trigger a vacuum when either one exceeded a threshold.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgppbxxrWfeta.pgp
Description: PGP signature
On Tue, Aug 07, 2007 at 10:18:32PM -0700, Jeremy Drake wrote:
> On Tue, 7 Aug 2007, Decibel! wrote:
>
> > ISTM that having a built-in array_to_set function would be awfully
> > useful... Is the aggregate method below an acceptable way to do it?
>
> Umm, the array_t
t;We're in the middle of shutting down" message over
"couldn't connect to the server", which is what the client would have
gotten anyway in very short order.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpKgVHQer2Ah.pgp
Description: PGP signature
4 +0530, Merlin Moncure wrote:
> > On 8/1/07, Decibel! <[EMAIL PROTECTED]> wrote:
> > > David Fetter and I just came up with these, perhaps others will find
> > > them useful:
> > >
> > > CREATE OR REPLACE FUNCTION array_to_set(anyarray, int) RETURNS S
system with log IO". While the following isn't
> production ready, it seems to have some really good ideas.
Is logging really the answer for that? ISTM it'd be better to provide
statistics info so that you could monitor autovacuum activity with
things like cricket, S
ps if we start that from now on? That will help as we move towards
> final reviews and commit. We seem to be discussing smaller aspects of
> the patch now.
Perhaps also posting a diff of the patch versions would help, so that
you can easily see exactly what code has changed since
> who have studied it, thoough most people don't seem to grasp what is going on
> in the system as a whole.
If someone's going to work on that, I'd much rather see the effort
expended on allowing the database to actually do this natively, since
it's something people ha
On Sat, Aug 04, 2007 at 12:46:32PM -0400, Tom Lane wrote:
> Decibel! <[EMAIL PROTECTED]> writes:
> > Something else to consider... normally you'd have to have a pretty
> > serious condition to run into this in normal usage, right? (I doubt
> > there's many folk
ar that the times are in GMT I think that's better.
Something else to consider... normally you'd have to have a pretty
serious condition to run into this in normal usage, right? (I doubt
there's many folks that use any debug level, let alone 3) I think that
gives us more f
's worth though, for sure. And in any case I'm not in a
hurry to
implement it.
I was referring specifically to the "read in what's not already in
shared buffers" part of Itagaki-san's message... that seems to be
something best suited for a bgreader.
--
Dec
to be deleted in the *future*.
Oh, but this should not be a problem, because a tuple is either frozen
or removed completely -- xmax cannot precede xmin.
What if it's frozen, then deleted, and then we wrap on xmax? Wouldn't
that make the tuple re-appear?
--
Decibel!, aka Jim Nasb
epted, or you could possibly put
something on pgFoundry. I'd set it up so that ascii() and chr() act
according to the appropriate locale setting (I'm not sure which one
would be appropriate).
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
Enterpr
201 - 296 of 296 matches
Mail list logo
