Tom Lane wrote:
> Dave Page <[EMAIL PROTECTED]> writes:
>> I can't imagine Flickr or Slashdot ...
>
> I'm pretty sure I remember reading that Slashdot had to put enormous
> amounts of cacheing in front of their DB to keep it from falling over
> on a regular basis.
Yes, slashdot and flickr both us
Tom Lane wrote:
>
> Exactly. VACUUM sucks (ahem) in all ways but one: it pushes the
> maintenance costs associated with MVCC out of the foreground query code
> paths and into an asynchronous cleanup task. AFAIK we are the only DBMS
> that does it that way. Personally I believe it's a fundamenta
Alvaro Herrera wrote:
> André Volpato wrote:
>
>> The ammount of space saved seems pretty clear to me.
>
> Yeah, zero most of the time due to alignment.
So trading off more I/O for less CPU?
I wonder if for any I/O bound database servers
it might be worth packing tightly rather than
aligning in
Chris Browne wrote:
>
> The server does not need the overhead of having *any* of the "X
> desktop" things running; it doesn't even need an X server.
>
> You don't need X running on the server in order use those "enterprise
> management" tools; indeed, in a "lights out" environment, that server
>
Tom Lane wrote:
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
>> On Wed, 8 Aug 2007, cluster wrote:
>>> Does anyone know where I can request an OR-version of plainto_tsquery()?
>
>> plainto_tsquery expects plain text, use to_tsquery for boolean operators.
>
> Are either of these definitions really
Scott Marlowe wrote:
> On 8/14/07, Harpreet Dhaliwal <[EMAIL PROTECTED]> wrote:
>> Hi,
>> I read a few lines about SP compilation in postgres
>>
>> http://searchoracle.techtarget.com/originalContent/0,289142,sid41_gci1179016,00.html
>>
>> 1. stored procedure compilation is transactional.
>> "You ca
Decibel! wrote:
> On Aug 15, 2007, at 2:11 PM, Gregory Stark wrote:
>> "Decibel!" <[EMAIL PROTECTED]> writes:
>>> On Wed, Aug 15, 2007 at 01:26:02PM -0400, Steve Madsen wrote:
On Aug 15, 2007, at 11:52 AM, Decibel! wrote:
> I can't really think of a case where a seqscan wouldn't return all
David Fetter wrote:
>> Dollar-quoting is a cute technical solution to that, but you can't
>> deny that it's simpler if you just restrict the function language to
>> be SQL-ish so that CREATE FUNCTION can parse it without any
>> interesting quoting rules. So sayeth Oracle and the SQL standards
>> c
Scott Marlowe wrote:
> On 8/14/07, john_sm <[EMAIL PROTECTED]> wrote:
>> Hey guys, for an enterprise wide deployment, what will you suggest and why
>> among - Red Hat Linux, Suse Linux and Ubuntu Linux, also, do you think, we
>> can negotiate the support pricing down?
>
> It's more about your skil
Denis Gasparin wrote:
>> Yeah, you're wrong. The difference is that plain vacuum does not try
>> very hard to reduce the length of a table file --- it just frees up
>> space within the file for reuse. vacuum full will actually move things
>> from the end of the file to free space nearer the head
Dann Corbit wrote:
> All of the database systems
> that I know of that use this column-oriented scheme are in-memory
> database systems. I don't know if Mr. Stonebraker's is also.
KDB+ (http://kx.com/) is column-oriented and has both on-disk
and in-memory capabilities http://kx.com/faq/#6 . It's
Greg Sabino Mullane wrote:
>> ...in favor of renaming the database "Horizontica".
>
> ...should definitely be "HorizonticaSQL"
Surely that should be capitalized "HorizonticASQL", no.
---(end of broadcast)---
TIP 9: In versions below 8.0, the plann
Chris Browne wrote:
> If I replicate your query, with extra columns, AND NAMES, I get the following:
>
> [EMAIL PROTECTED]:5433=# select random() as r1, random() as r2, random() as
> r3 from generate_series(1,10) order by random();
> r1 | r2 |r3
>
Joshua D. Drake wrote:
> On Mon, 26 Nov 2007 10:28:03 -0800 (PST)
> Richard Broersma Jr <[EMAIL PROTECTED]> wrote:
>> --- On Mon, 11/26/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>>> In "theory" the item that would be a natural key
>>> in this instance is the VIN.
And you then need to deal wi
Gregory Stark wrote:
> We're not goldfish, we can remember the topic of discussion for at least a few
> hours.
So can Goldfish. Apparently they have a 3-month+ memory.
http://nootropics.com/intelligence/smartfish.html
http://en.wikipedia.org/wiki/MythBusters_(season_1)#Goldfish_Memory
With a me
Cindy Parker wrote:
> ...choice of Oracle or PostgreSQL for the back-end...
> Can you help me compare PostgreSQL to SQL Server and/or Oracle? Do
> you know of any websites or blogs that discuss these issues? ...
> I did look at http://sql-info.de/postgresql/postgres-gotchas.html, an
> excellent pa
Chris Browne wrote:
> [EMAIL PROTECTED] (Zoltan Boszormenyi) writes:
>> SELECT COUNT(*)
> [Waving hands for a moment]
Would what Chris describes below be a good candidate for
a pgfoundry project that has functions that'll create the
triggers for you? (yeah, I might be volunteering, but would
undo
Scott Marlowe wrote:
>> In particular, MySQl seems to have richer string functions to parse
>> out sub strings and als trim a string for automatic table insertion
>> from long multifield strings.
>
> Have you read the postgresql manual on string functions? Seriously,
> it's easily a match for MyS
Pavel Stehule wrote:
> 2010/10/8 Carlos Mennens :
>> I know that MySQL uses MyISAM storage engine by default... what
>> storage engine does PostgreSQL use by default ...
>
> PostgreSQL supports and uses just only one storage engine - PostgreSQL.
That said, ISTM one of Postgres's bigger strengths
Lincoln Yeoh wrote:
> What's more important to such companies is the ability to scale over
> multiple machines.
That question - how much work it is to administer thousands of database
servers - seems to have been largely missing from this conversation.
Apparently back in 2008, Facebook had 1800 M
Glen Parker wrote:
> As was already mentioned, application logs. Unlogged tables would be
> perfect for that, provided they don't go *poof* every now and then for
> no good reason. Nobody's going to be too heart broken if a handful of
> log records go missing, or get garbled, after a server crash
Josh Berkus wrote:
>> With the current patches, the data survives a restart just fine.
>
> Per -hackers, that's not guarenteed.
"Not guaranteed" is fine. What people are asking for is "often survives".
AFAIK we don't truncate the log file created by the log_filename GUC
on every unclean crash an
Eric McDonald wrote:
> Greetings All:
>
> Does anyone here have any insight on to what EAL level Postgres is at
> for DOD/Military installations? I see that there's an SE-Linux
> fortified version on the Wiki, but no certifications are listed in the
> contents.
>
> Any direction to certification
Webb Sprague wrote:
> On Feb 1, 2008 2:31 AM, Enrico Sirola <[EMAIL PROTECTED]> wrote:
>> I'd like to perform linear algebra operations on float4/8 arrays...
>
> If there were a coherently designed, simple, and fast LAPACK/ MATLAB
> style library and set of datatypes for matrices and vectors in
>
Webb Sprague wrote:
> On Feb 1, 2008 12:19 PM, Ron Mayer <[EMAIL PROTECTED]> wrote:
>> Webb Sprague wrote:
>>> On Feb 1, 2008 2:31 AM, Enrico Sirola <[EMAIL PROTECTED]> wrote:
>>>> ...linear algebra ...
>>> ... matrices and vectors .
>> ...E
Ted Byers wrote:
> --- Webb Sprague <[EMAIL PROTECTED]> wrote:
>>> ...linear algebra ...
>> ... matrices and vectors .
> ...Especially if some GIST or similar index
>> could efficiently search
> for vectors "close" to other vectors...
>
> I see a potential problem here, in terms of
Josh Berkus wrote:
Id really prefer my company be certified by the community rather than by
a company, despite the full respect I have in SRA's engagement in
PostgreSQL and that we all know their contributions.
What would it mean for a company to be certified?
I'd hope it'd mean that I can have
If one wanted to dump some postgres databases for long term
archival storage (maybe decades), what's the recommended
dump format? Is the tar or plain text preferred, or is
there some other approach (xml? csv?) I should be looking
at instead?
Or should we just leave these in some postgres
databa
Greg Smith wrote:
On Fri, 14 Mar 2008, Andrej Ricnik-Bay wrote:
A silly question in this context: If we know of a company that does
use PostgreSQL but doesn't list it anywhere ... can we take the
liberty to publicise this somewhere anyway?
I notice Oracle (and sleepycat before them) had a lo
Zdeněk Kotala wrote:
1) What type of names do you prefer?
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
There are many precedents. "cvs update", "git pull"
"apt-get install".
Anyone else like this approach?
Of the choice
Clodoaldo wrote:
...IBM is investing...What does it mean for Postgresql?
One cool thing it means is that there are now *two*
companies (thanks again Fujitsu) bigger than
Oracle backing (to some extent) Postgres.
And now one company bigger than Microsoft.
Yeah, this doesn't affect the communit
Tom Lane wrote:
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I
Tom Lane wrote:
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
...a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I'll second
Ben wrote:
I'm working on a project which requires me to keep track of objects,
each of which can have an arbitrary number of attributes. Although there
will be many attributes that an object can have,...
Anyway, this seems like a common problem without a perfect solution, and
I'm sure people m
Magnus Hagander wrote:
Craig Ringer wrote:
with a version of PostgreSQL with the same minor version as the one
you were using on the server, eg if you were using 8.1.4 you should
get the latest PostgreSQL in the 8.1 series (NOT 8.2 or 8.3) to try
to read the data.
What you mean here is of cour
Lincoln Yeoh wrote:
At 10:30 PM 6/24/2008, David Siebert wrote:
Which disto is best for running a Postgres server?
Just to add one more slightly different philosophy.
For servers I manage, I run the most conservative
and slow changing distros that only update security
releases (Debian Stable,
Finally got around to looking at this thread.
Looks like the original questions from the thread
got resolved, but I found this behaviour surprising:
regression=# select interval '1' day to second;
interval
--
@ 1 hour
(1 row)
Should this be 1 second?
If so I can send a patch.
regre
Tom Lane wrote:
> Ron Mayer writes:
>> Looks like the original questions from the thread
>> got resolved, but I found this behaviour surprising:
>
>> regression=# select interval '1' day to second;
>> interval
>> --
>> @ 1 hour
>
Tom Lane wrote:
> I wrote:
>> I'm inclined to say that these two cases are out of line with what
>> the rest of the code does and we should change them.
> ...
> Now, all three of these cases throw "invalid input syntax" in 8.3,
> so this is not a regression from released behavior. The question
>
Tom Lane wrote:
> Ron Mayer writes:
>> regression=# select interval '1 1' hour;
>
> Hmm, not sure about that one. We decided a week or two back that we
> don't want the thing discarding higher-order field values, and this
> seems pretty close to that.
Sam Mason wrote:
> It all depends on the problem domain of course, but this seems to work
> OK for us! I really want to hack Samba around so that the users can
> view the files directly from inside the database, but I'm not sure how
> good an idea this really.
"hack Samba"? Wouldn't it be easie
Drifting off topic so I'm no longer ccing the lists.
Sam Mason wrote:
>
>> The perl Fuse::DBI module's example sounds pretty similar to the
>> system you described where he "file" seems to be a column in a table.
>> http://www.rot13.org/~dpavlin/fuse_dbi.html
>
> FUSE looks pretty easy to get g
On Mon, Nov 02, 2009 at 10:52:40AM +, Jasen Betts wrote:
> what's the absolute value of '1month -30 days'::interval
Curious what a use case for taking the absolute value
of such mixed intervals might be.
I could imagine such intervals being used for stuff like
"XXX is due in Y months but need
Tom Lane wrote:
Maxim Boguk <[EMAIL PROTECTED]> writes:
[ ndistinct estimates way off ]
Estimating the number of distinct values in a distribution with a long
tail is just a really hard problem :-(
If I have a table where I know it has this property, is there
any way I can tell autovacuum's
http://archives.postgresql.org/pgsql-patches/2003-09/msg00121.php
[3] http://archives.postgresql.org/pgsql-patches/2003-12/msg00253.php
Ron Mayer
(formerly [EMAIL PROTECTED] who
posted those ISO-8601 interval patches)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Ron Mayer wrote:
Tom Lane wrote:
Or someone could try to make it work, but given that no one has taken
the slightest interest since Tom Lockhart left the project, I wouldn't
hold my breath waiting for that.
I have interest. For 5 years I've been maintaining a patch for a client
You might want to try using a file system (ZFS, NTFS) that
does compression, depending on what you're trying to compress.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Grant Allen wrote:
...warehouse...DB2...IBM is seeing typical
storage savings in the 40-60% range
Sounds about the same as what compressing file systems claim:
http://opensolaris.org/os/community/zfs/whatis/
"ZFS provides built-in compression. In addition to
reducing space usage by 2-3x, co
Chris Browne wrote:
There's a way that compressed filesystems might *help* with a risk
factor, here...
By reducing the number of disk drives required to hold the data, you
may be reducing the risk of enough of them failing to invalidate the
RAID array.
And one more way.
If neither your databas
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
I also was confused by its flatness. I am finding the email traffic
almost impossible to continue tracking, so something different is
happening, but it seems it is not volume-related.
Yes, my perception also is tha
Joshua D. Drake wrote:
On Fri, 2008-11-21 at 08:18 -0800, Ron Mayer wrote:
Bruce Momjian wrote:
Tom Lane wrote:
... harder to keep
up with the list traffic; so something is happening that a simple
volume count doesn't capture.
If measured in "bytes of the gzipped mbox" it ..
Tom Lane wrote:
Ron Mayer <[EMAIL PROTECTED]> writes:
Joshua D. Drake wrote:
Its because we eliminated the -patches mailing list.
That's part of it. I've added -patches to the graph at
http://0ape.com/postgres_mailinglist_size/ as well as
a graph of hackers+patches combin
Zagato wrote:
I have som SQL that in 8.0.3 do:
# SELECT '32 hours'::INTERVAL;
interval
-
@ 1 day 8 hours
And in 8.3.5 do:
seg_veh2=# SELECT '@ 32 hours'::INTERVAL;
interval
@ 32 hours
Why i unable to get my old style of interval, i really need to see the
da
Grzegorz Jaśkiewicz wrote:
true, if you don't want to search on values too much ,or at all - use
float[]. But otherwise, keep stuff in a tables as such.
It might be humongous in size, but at the end of the day - prime thing
when designing a db is speed of queries.
If he's worried about speed
Scott Marlowe wrote:
> Actually, it's usually the drives that lie about fsync, especially
> consumer grade (and some server grade) SATA / PATA drives are known
> for this.
I'm still looking for any evidence of any drive that lies.
Is there actually a drive which claims to support the
IDE "FLUSH_C
Craig Ringer wrote:
> On 16/12/2009 9:07 AM, Scott Marlowe wrote:
>> I'd also recommend moving off of OSX as you're using a minority OS as
>> far as databases are concerned, and you won't have a very large
>> community to help out when things do go wrong
>
> It sounds like PostgreSQL is being used
Lincoln Yeoh wrote:
> Ten or so years ago MySQL was better than Postgres95, and it would have
> been easy to justify using MySQL over Postgres95 (which was really slow
> and had a fair number of bugs). But Postgresql is much better than MySQL
> now. That's just my opinion of course.
Really?!?
MyS
Gauthier, Dave wrote:
> The arguments against PG are not technical.
A few more points that I didn't see in this thread yet that might help
answer the non-technical questions:
* There seem to be more commercial vendors providing support
for Postgres than MySQL - because most mysql support came
On this first day of the month, I thought it might be interesting
to re-visit the conventional wisdom about postgres vs mysql.
Do these seem like fair observations?
Storage engines - Advantage Postgres for having far more available.
Postgre has such a wide range of storage engines to choose fr
Gregory Stark wrote:
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
* The capitalization that makes everyone (customers, execs, etc) I introduce
it to parse the name as Postgre-SQL.
*
Gregory Stark wrote:
> One thing which has *not* been mentioned which i find positively shocking is
> VACUUM. This was once our single biggest source of user complaints. Between
> Autovacuum improvements and HOT previously and the free space map in 8.4 the
> situation will be much improved.
The ot
Ivan Sergio Borgonovo wrote:
> On Fri, 20 Feb 2009 06:50:22 -0800
> David Fetter wrote:
>>> ... moving some of the checks
>>> into the database and away from the application.
>> Since a useful database has *many* applications instead of "the"
>> application, I think this is an excellent move.
>
>
Joshua D. Drake wrote:
> On Wed, 2009-02-25 at 09:21 +0900, Jordan Tomkinson wrote:
>> On Wed, Feb 25, 2009 at 12:05 AM, Aidan Van Dyk
>> wrote:
>> * Greg Smith [090201 00:00]:
>> > Shouldn't someone have ranted about RAID-5 by this point in
>> the thread?
>> You m
Joshua D. Drake wrote:
> On Fri, 2009-02-27 at 10:19 +1300, Tim Uckun wrote:
>>
>> [according to some page on the web site...]
>> 8.4 was scheduled to be released march 1. Do we know what the
> All schedules are subject to change within the community :)
>> tentative date of release is?
Joshua D. Drake wrote:
> On Thu, 2009-02-26 at 15:27 -0800, Ron Mayer wrote:
>> Joshua D. Drake wrote:
>>> On Fri, 2009-02-27 at 10:19 +1300, Tim Uckun wrote:
>>>>
>>>> 8.4 was scheduled to be released march 1. ...
>>
>> I do notice that
Greg Smith wrote:
> There are some known limitations to Linux fsync that I remain somewhat
> concerned about, independantly of LVM, like "ext3 fsync() only does a
> journal commit when the inode has changed" (see
> http://kerneltrap.org/mailarchive/linux-kernel/2008/2/26/990504 ). The
> way files
Marco Colombo wrote:
> Ron Mayer wrote:
>> Greg Smith wrote:
>>> There are some known limitations to Linux fsync that I remain somewhat
>>> concerned about, independantly of LVM, like "ext3 fsync() only does a
>>> journal commit when the inode ha
Tom Lane wrote:
> Adrian Klaver writes:
>> Nothing. I have created a Postgres instance on an EC2 virtual machine with
>> attached EBS(Elastic Block Storage)..[...]
>
> ... I wonder whether you have any guarantees about database consistency
> in that situation? PG has some pretty strong requirem
Marco Colombo wrote:
> Yes, but we knew it already, didn't we? It's always been like
> that, with IDE disks and write-back cache enabled, fsync just
> waits for the disk reporting completion and disks lie about
I've looked hard, and I have yet to see a disk that lies.
ext3, OTOH seems to lie.
ID
Sam Mason wrote:
> On Wed, Apr 08, 2009 at 04:56:35PM +0100, Ian Mayo wrote:
>> One more thing: hey, did you hear? I just got some advice from Tom Lane!
>
> Statistically speaking; he's the person most likely to answer you by
Even so, this might be the #1 advantage of Postgres over Oracle (cost
Robert Treat wrote:
>
> You can be sure that discussion of this topic in this forum will soon be
> visited by religious zealots, but the short answer is "nulls are bad, mmkay".
>
> A slightly longer answer would be that, as a general rule, attributes of your
> relations that only apply to 1%
Rick Schumeyer wrote:
> I want to be able to search a list of articles for title words as well
> as author names I'm not sure the best strategy for the names. The
> full text parser "parses" the names giving undesirable results.
>
> For example,
>
> select to_tsvector('claude Jones');
>
Alban Hertroys wrote:
> On May 2, 2009, at 9:33 AM, Mike Christensen wrote:
>
>> ...
>> create table Threads ( ... Tags int2[], ...);
>>
>> To me this seems cleaner, but I'm wondering about performance. If I
>> had millions of threads, is a JOIN going to be faster? ...
>
> ...I don't think ar
Sam Mason wrote:
> You get an error because " 123 11" isn't a valid literal of an
> (undecorated) INTERVAL type.
Hmm. should it be?
Skimming the spec makes me think it might be a valid day-time interval.
Quoting the spec:
::=
[ ] { | }
...
::=
|
::=
[ [
[ ] ] ]
Short summary:
I find this tiny (9-line) patch useful to help my clients know
when FSM settings may need updating.
Some of the more frequently asked questions here are in regards to FSM
settings. One hint I've seen is to run "vacuum verbose;". At the end
of thousands of lines of INFO and
On Wed, 23 Feb 2005, Tom Lane wrote:
> Ron Mayer <[EMAIL PROTECTED]> writes:
> > +if (needed > MaxFSMPages)... ereport(WARNING, ...
>
> An unconditional WARNING seems a bit strong to me for a case that is not
> necessarily wrong.
How about a HINT, not unlike the
Thanks everyone for the feedback on my patch.
Objections I've heard (both online and in email) included:
* WARNING is too strong for possibly OK behavior
* It's similar to "checkpoints occuring too frequently...
consider increasing...checkpoint_segments" which
is a LOG
On Thu, 24 Feb 2005, Tom Lane wrote:
> I preferred Simon's idea of not trying to produce a warning for pages
> when we've detected relation overflow.
Sounds good. I'll make that update.
Should the relation overflow be a WARNING or a LOG? It sounds like
if you have that problem it's almost cert
On Thu, 24 Feb 2005, Ron Mayer wrote:
> Should the relation overflow be a WARNING or a LOG? It sounds like
> if you have that problem it's almost certainly a problem, right?
And while I'm at it... what's the convention for INFOs vs LOGs?
The "checkpoint...too frequent
On Thu, 24 Feb 2005, Tom Lane wrote:
> I'd go for making them both LOG, I think. More consistent.
Ok, here's another try :) With a couple more questions...
1. If I read Simon's email correctly, it implied that he wanted to see
the "free space map" message for a VACUUM even when VERBOSE
On Fri, 25 Feb 2005, Bruce Momjian wrote:
> Tom Lane wrote:
> > Ron Mayer <[EMAIL PROTECTED]> writes:
> > > Should the relation overflow be a WARNING or a LOG? ...
> > I'd go for making them both LOG, I think. More consistent.
>
> Can we also update thi
Did anyone get multi-column GIST indexes working using both
the gist_btree and postgis modules?
It seems to work fine for me on small test cases (shown
at the bottom), but seems to crash my database for large
ones. Any advice is welcome - including pointers to better
lists to ask questions like t
On Sun, 27 Feb 2005, Simon Riggs wrote:
> On Fri, 2005-02-25 at 16:48 -0800, Ron Mayer wrote:
> > Getting closer?
> For me, yes. [...]
> The not-warnings seem a little wordy for me, but they happen when and
> how I would hope for.
>
> So, for me, it looks like a pol
When you VACUUM a table with postgis indexes (perhaps GIST indexes
in general?) it seems a lock is held on the table. Setting
vacuum_cost_delay seems to make vacuum hold this lock much longer.
Is this true?
If so, I assume that's not desirable behavior, right? It makes
autovacuum harder to
On Mon, 28 Feb 2005, Tom Lane wrote:
>
> You could shorten the intervals for which the lock is held by reducing
> vacuum_mem, but this might be counterproductive overall.
Does this work?
I just tried:
setting vacuum_mem=1024
setting vacuum_cost_delay=10
ran a while loop that repea
to both the client and the logs
by default.
-------
Ron Mayer wrote:
On Sun, 27 Feb 2005, Simon Riggs wrote:
On Fri, 2005-02-25 at 16:48 -0800, Ron Mayer wrote:
Getting closer?
For me, yes. [...]
The not-warnings seem a little wordy for me, but they happen when and
how I would hope for.
Bruce Momjian wrote:
You didn't like server_min_messages = 'notify'?
I merely don't have a feeling for how much additional stuff
verbose would be putting in the log files.
If it's a good practice for production systems to be logging
NOTIFY's I'm happy with the change.
My reasoning why I thought the
If one of the contrib modules (int_array_aggregate in contrib/intagg) is
crashing my backend, where's a good place to report a bug or get hints
where to look further?
It seems to work fine on small arrays, but crashes on large ones.
The second query would have put about 500 rows in the aggrega
Tatsuo Ishii wrote:
Is there anyway to load balance selects to more than 2 servers? ex. 1 master with 2 slaves? Run multiple instances?
It's on my TODO but will not be a trivial change.
Could I set up 2 pairs of pgpool-balanced servers, and use a
third pgpool to load balance across the two pools?
Tom Lane wrote:
Bart Grantham <[EMAIL PROTECTED]> writes:
# SELECT * FROM connections WHERE connectee_node_id = ANY (ARRAY[28543,28542]
);
[ performance sucks ]
Yeah :-(. The = ANY (array) notation is new in the last release or so,
and is completely without optimization of any kind. Turn it int
Marco Colombo wrote:
That is, given a variable A, you can always write a boolean expression
that evaluates True or False to test if A is _equal_ to None/undef/NULL
(in C):
And of course you can do this in SQL as well.
('a', NULL) is neither the same _nor different_ from ('a', 2).
Uh, I'm not sure w
Bart Grantham wrote:
Hello again. I had a problem a few weeks ago with using IN ( some_array
) having really rough performance. Special thanks to Ron Mayer for the
suggestion of using int_array_enum(some_array) to join against. I had
to upgrade to PG8 but that technique works really well
Mark Steckel wrote:
I have also scrounged the Internet looking for examples of
Postgres being used in government, preferably in 24x7 capacities.
I find googling for vendors who are known to use PostgreSQL and
searching for people's resumes is a good way to find descriptions
of Government project
Martijn van Oosterhout wrote:
Well, you get another issue, alignment. If you squeeze your string
down, the next field, if it is an int or string, will get padded to a
multiple of 4 negating most of the gains. Like in C structures, there
is padding to optimise access.
Anecdotally I hear at leas
Jim C. Nasby wrote:
On Thu, Jul 14, 2005 at 11:29:23PM +0200, Martijn van Oosterhout wrote:
On Thu, Jul 14, 2005 at 11:30:36AM -0500, Jim C. Nasby wrote:
On Wed, Jul 13, 2005 at 07:52:04PM -0400, Bruce Momjian wrote:
This is a good point. We have always stored data on disk that exactly
match
Andrus wrote:
Then redesign this as a many to many relation. ...
This means adding separate row for each department into permission table.
Not really.
You can of course store an Array of department IDs in that same table.
That would probably cause the minimum impact on your queries too.
---
Dann Corbit wrote:
There is a "privacy hole" from using the MAC address. (Read it in the
WIKI article someone else posted).
Probably, it would be better to use a one way hash of the MAC address.
The chances of MAC addresses colliding (through some low-end network
card vendor's sloppy manufac
Greg Stark wrote:
clustering...
That will only help if you're often retrieving moderately large result sets by
one particular index. If you normally only retrieve one record at a time or
from lots of different indexes then it probably won't really make much
difference.
It'll also help for colu
Richard Huxton wrote:
While the other answers all do their job, and in one go too, I'd be
surprised if you found anything faster than:
SELECT myval FROM mytable WHERE myval > 1234 ORDER BY myval LIMIT 1
Really? Aren't most things with ORDER BY O(n*log(n))?
Or is the optimizer smart enou
Tom Lane wrote:
It wouldn't be hard that I can see (just build hash and btree opclasses
for tid), but I'm pretty unclear on why bother. There's no use-case for
cross-table joins involving ctid, since you couldn't usefully store a
ctid referencing another table. The example Ilja showed was quit
1 - 100 of 149 matches
Mail list logo
