cluster order on a
table. You would look in the clustering index for the closest value
to your key and where it is in the heap and then ask for a page in
that neighborhood. (You'd probably want to look at more than just one
index tuple, but you get the idea).
--
Decibel!, aka Jim C. Nasby
on it.
+1. It might be possible to get screwed by not doing a distclean, but
the build time savings seems worth it (first thing I do if I get a
build error is make clean/distclean).
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy
less
wasteful than further compounding lock contention for the WAL. Even
if it does result in more overall IO, you have to trade a *lot* of IO
to balance out the impact of lock contention.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy
a dump/
reload (maybe the upgrade stuff would make this possible?)
--
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
of issues with the FS itself. Not to
mention that changing filesystems on a large production system is
very painful.
--
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
for this...
--
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
it in for 8.4.
--
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
touched it during recovery, we'd be able to detect torn
pages, yet still recover. That would help show that torn pages aren't
possible in a particular environment (though unfortunately I don't
think there's any way to actually prove that they're not).
--
Decibel!, aka Jim C. Nasby, Database
On Oct 5, 2008, at 8:50 PM, Greg Smith wrote:
Patch v3 attached that exposes boot_val and reset_val. The docs
for the latter link to the RESET command page for details.
nitpickIs it really that important that we save 2 characters on
each field name?/nitpick
--
Decibel!, aka Jim C. Nasby
hints (and
that's *exactly* what OFFSET 0 is).
--
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
to use the oid instead like we do
with
pg_class.
It would be really nice to have the table OID in pg_tables. That was
one of the driving forces behind the pg_newsysviews project.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy
On Oct 1, 2008, at 12:12 AM, Gurjeet Singh wrote:
On Wed, Oct 1, 2008 at 9:39 AM, Tom Lane [EMAIL PROTECTED] wrote:
Gurjeet Singh [EMAIL PROTECTED] writes:
On Wed, Oct 1, 2008 at 3:07 AM, Decibel! [EMAIL PROTECTED]
wrote:
ERROR: aggregates not allowed in WHERE clause
No, the real issue
for an attribute would
improve this.
Sadly, I don't have time to work on any of this. But these things are
issues to my company, and we do have money. ;)
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
support this aspect as
well.
+1. And for everyone who immediately jumped to NORMALIZE! as the
answer, consider that that means a bare minimum of 24 bytes overhead
per item that would go into the array. It's not hard at all for that
overhead to become massive.
--
Decibel!, aka Jim C. Nasby
to assuming a good format and only fail
back to something else if that doesn't work?
--
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
ISTM it'd be useful to have an array_length function (since I just
wrote one for work ;), so here's a patch. Note that I don't have the
docs toolchain setup, so I wasn't able to test the doc patches.
array_length.patch
Description: Binary data
--
Decibel!, aka Jim C. Nasby, Database
quickly if you had a lot of different
queries you were running.
Of course, someone could always just setup a cron job to grab the
stats once a minute, so if this greatly complicates the patch I
wouldn't worry about it.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give
, they won't be
so blind. I think just adding the HINT is good enough.
Since this is something that's not supposed to happen, making it a
WARNING might be appropriate too...
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net
? Promoting seqscans in an OLTP
environment seems to be a really bad idea to me...
--
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
sleeves or dangling a carrot (money)
in front of some of the people that do consulting and back-end hacking.
--
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
On Oct 17, 2008, at 4:30 AM, Vladimir Sitnikov wrote:
Decibel! [EMAIL PROTECTED] wrote:
I had tried to use a normal table for store stats information,
but several acrobatic hacks are needed to keep performance.
I guess it is not really required to synchronize the stats into
some physical
On Oct 21, 2008, at 12:06 PM, Tom Lane wrote:
Jim 'Decibel!' Nasby [EMAIL PROTECTED] writes:
WHERE 'xxx' IN (people.home_phone, people.work_phone,
people.mobile_phone)
Yeah, not exactly a common case, but at least in 8.1 this was turned
into a set of ORs. Starting in 8.2
= NULL, installment_date = NULL
NOT v_prev IS NULL = t, v_prev IS NULL = f
NOT v_next IS NULL = f, v_next IS NULL = t
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
On Oct 24, 2008, at 7:19 PM, Tom Lane wrote:
Decibel! [EMAIL PROTECTED] writes:
Was anything ever done with http://archives.postgresql.org/pgsql-
hackers/2008-09/msg01758.php ?
No, we got stalled on what the behavior really ought to be:
http://archives.postgresql.org/pgsql-hackers/2008-09
to begin with.
That leaves the mixed RHS case. If it's cheap to just split things
into two piles (fixed RHS vs variable RHS) then that's probably the
way to go. Ideally, each condition would then be estimated
separately, and the executor would favor executing the cheaper one
first.
--
Decibel
, min_update_trigger: not called for each row);
--
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
or configure.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
if it wasn't
bloating pg_class all the time.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
://www.postgresql.org/mailpref/pgsql-hackers
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
is this needed at all?
I suspect this is to deal with needing to reserve space in a cluster
that you're planning on upgrading to a new version that would take
more space, but I think the implementation is probably too simplistic.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED
On Nov 9, 2008, at 11:44 AM, Tom Lane wrote:
Decibel! [EMAIL PROTECTED] writes:
On Nov 8, 2008, at 3:08 PM, Tom Lane wrote:
... It's reasonably common for pg_xlog to be a symlink.
ISTM it'd be better still to have an official knob that allows you to
determine where pg_xlog lives. ISTR
-
defined dimension means, but I can't see how the results of that
should vary between array_length and array_lower/upper.
Is there some other corner case?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
paint ourselves into a corner, or should we just wait until
8.5?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
suddenly
become updateable.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
.
IIRC the community did come to a consensus on allowing for a
different logical ordering from physical ordering, it was an issue of
actually doing the work. If this is an itch you want to scratch, you
might look into fixing that problem instead.
--
Decibel!, aka Jim C. Nasby, Database
close to an ideal value. If
we start slowly increasing it then at least we can start seeing where
people start having issues with query plan time.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent
still have to
eventually freeze a write-mostly table.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
about additional stats to collect. :)
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
, and a lot of those
don't necessarily need a lot of hand tuning beyond the stats target.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
of
this at a time. There would be value in only allowing logical order
to differ from literal order, or only allowing physical order to
differ. That means you could tackle just one of those for the first
go-round and still get a benefit from it.
--
Decibel!, aka Jim C. Nasby, Database
(
a int
, b int
) TO someuser;
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
~5MB/s, but
during recovery we'll only do 600-700kB/s. I've never straced a
backend to see exactly what's going on.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
--
Sent via pgsql-hackers mailing list
On Dec 1, 2009, at 12:58 PM, Tom Lane wrote:
The bottom line here seems to be that the only practical way to do
anything like this is to move the hint bits into their own area of
the page, and then exclude them from the CRC. Are we prepared to
once again blow off any hope of in-place update for
On Dec 1, 2009, at 1:39 PM, Kevin Grittner wrote:
Josh Berkus j...@agliodbs.com wrote:
And a lot of our biggest users are having issues; it seems pretty
much guarenteed that if you have more than 20 postgres servers, at
least one of them will have bad memory, bad RAID and/or a bad
driver.
On Dec 1, 2009, at 4:13 PM, Greg Stark wrote:
On Tue, Dec 1, 2009 at 9:57 PM, Richard Huxton d...@archonet.com
wrote:
Why are we writing out the hint bits to disk anyway? Is it really so
slow to calculate them on read + cache them that it's worth all this
trouble? Are they not also to blame
On Dec 3, 2009, at 1:53 PM, Jonah H. Harris wrote:
On Tue, Dec 1, 2009 at 1:27 PM, Joshua D. Drake
j...@commandprompt.com wrote:
On Tue, 2009-12-01 at 13:20 -0500, Robert Haas wrote:
Does $COMPETITOR offer this feature?
My understanding is that MSSQL does. I am not sure about Oracle. Those
On Dec 11, 2009, at 8:44 PM, Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Ashish wrote:
I am thinking about starting with the following TODO item:
-- Have EXPLAIN ANALYZE issue NOTICE messages when the estimated
and actual row counts differ by a specified percentage.
I even have
On Dec 15, 2009, at 5:40 PM, Jeff Davis wrote:
If you think I'm proposing that we drop inclusivity/exclusivity before
telling the application, that's not what I'm proposing at all. I'm
proposing that, at least in some circumstances, it's important to be
able to display the same value in
On Dec 15, 2009, at 11:34 AM, Jeff Davis wrote:
On Tue, 2009-12-15 at 10:19 -0500, Tom Lane wrote:
I'm not sure that anyone has argued that. I did suggest that there
might be a small list of types for which we should provide discrete
behavior (ie, with next/previous functions) and the rest
On Dec 22, 2009, at 12:54 PM, Simon Riggs wrote:
9. Create a recovery command file in the standby server with parameters
required for streaming replication.
7. (a) Make a base backup of minimal essential files from primary
server, load this data onto the standby.
10. Start postgres in the
On Dec 19, 2009, at 9:52 PM, Robert Haas wrote:
On Sat, Dec 19, 2009 at 10:46 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Bruce Momjian wrote:
Seems I need some help here.
I'm willing to work on this --- it doesn't look particularly fun but
we really need it.
You don't
On Dec 19, 2009, at 4:38 PM, Robert Haas wrote:
On Sat, Dec 19, 2009 at 1:56 PM, Caleb Welton cwel...@greenplum.com wrote:
I maintain that the approaches that inform the user that they have met that
condition via ALTER statement failures (Postgres/DB2/Microsoft Bound Views)
have certain
On Dec 15, 2009, at 6:29 PM, Jeff Davis wrote:
On Tue, 2009-12-15 at 18:06 -0600, decibel wrote:
Now that varlena's don't have an enormous fixed overhead, perhaps it's
worth looking at using them. Obviously some operations would be
slower, but for your stated examples of auditing and history
On Dec 29, 2009, at 6:29 PM, Tom Lane wrote:
* when a tabstat message comes in, increment changes_since_analyze by
the sum of t_tuples_inserted + t_tuples_updated + t_tuples_deleted;
* when an analyze report message comes in, reset changes_since_analyze
to zero.
If that's being added, could
On Dec 30, 2009, at 9:50 PM, Bruce Momjian wrote:
3) There is no easy way to analyze all databases. vacuumdb --analyze
does analyze _and_ vacuum, which for an 8.4 to 8.5 migration does an
unnecessary vacuum. Right now I recommend ANALYZE in every database,
but it would be nice if there were
On Jan 6, 2010, at 1:52 AM, decibel wrote:
On Dec 30, 2009, at 9:50 PM, Bruce Momjian wrote:
3) There is no easy way to analyze all databases. vacuumdb --analyze
does analyze _and_ vacuum, which for an 8.4 to 8.5 migration does an
unnecessary vacuum. Right now I recommend ANALYZE in every
On Jan 6, 2010, at 5:46 PM, Andrew Dunstan wrote:
Tim Bunce wrote:
I was investigating a bug in an 8.4.1 production system and distilled a
test case down to this:
CREATE OR REPLACE FUNCTION bar() RETURNS integer AS $$
#die 'BANG!'; # causes server process to exit(2)
#
, 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]
EnterpriseDB http
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 Nasby[EMAIL
, 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.
--
Decibel!, aka Jim Nasby[EMAIL
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 flexibility.
--
Decibel!, aka Jim Nasby
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 folks that use any debug level, let alone 3) I
the database to actually do this natively, since
it's something people have been asking for forever.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgp9RiKz5Gtqj.pgp
Description: PGP signature
. 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 last time...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http
be better to provide
statistics info so that you could monitor autovacuum activity with
things like cricket, SNMP, etc.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpQAGIJLuS1i.pgp
Description: PGP signature
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 SETOF
anyelement LANGUAGE SQL AS $$
SELECT $1[i] from generate_series
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
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_to_set function is not an aggregate
a threshold.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgppbxxrWfeta.pgp
Description: PGP signature
?
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://enterprisedb.com 512.569.9461 (cell)
pgpxPBiJIwcPJ.pgp
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
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
.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpkDxwB7dNwA.pgp
Description: PGP signature
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
; 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[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell
...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpGfcyDpEN3F.pgp
Description: PGP signature
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 as being able to see all the databases
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 Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com
... 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... anything but full, which is constantly
confused with a full database vacuum.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB
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 measures isn't to make it impossible
to break the security, it's to make it more difficult than it's worth.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED
that's 5 years old...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpv9MZhCTRdP.pgp
Description: PGP signature
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, simple
or not.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB
by
standing up really fast. -- Jonathan Katz
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB
the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpM1sQ9YWbpd.pgp
Description: PGP signature
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]:
TODO item?
+ If your life is a hard drive, Christ can be your
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 be even better if one XID could be shared across backends.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB
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://enterprisedb.com
notes... they go way back.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpTmJemIG86f.pgp
Description: PGP signature
cases for table partitioning.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpKGvmIPLYTD.pgp
Description: PGP signature
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
, 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 Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http
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 does not use a
super user, you
README cleanup so
the
doc system works better.
One question... 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
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 Nasby
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 warning, but making this a hard
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
get the labels programmatically as well as via psql.
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http
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 except on
local (a.k.a. Unix domain socket
...
--
Decibel!, aka Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpWfs9AG9Wy9.pgp
Description: PGP signature
the network is well enough run that, even if you
did run it, it would not represent a real risk.)
ISTM that if someone breaches your network to the point where they can
spoof identd, you're pretty much hosed anyway; so what's the point of
hard-coding passwords in a config file somewhere then?
--
Decibel
1 - 100 of 293 matches
Mail list logo
