What about the pgpass file?
https://www.postgresql.org/docs/9.2/static/libpq-pgpass.html
On 11/17/2017 03:06 PM, marcelo wrote:
I need to "emulate" the pg_dump code because the password prompt. Years
ago I write a program (for the QnX environment) that catched some prompt
and emulates the sta
On 11/17/2017 02:23 PM, John R Pierce wrote:
On 11/17/2017 12:19 PM, marcelo wrote:
Sorry, I was not exact.
I don't need nor like to change pg_dump. Rather, based on pg_dump code, I
need to develop a daemon which can receive a TCP message (from a
privileged app) containing some elements: the d
On 11/16/2017 03:13 PM, bricklen wrote:
On Thu, Nov 16, 2017 at 1:07 PM, Ron Johnson <mailto:ron.l.john...@cox.net>> wrote:
v9.2.7 (Yes, I know, it's old. Nothing I can do about it.)
During a "whole database" restore using pg_restore of a custom dump,
w
Hi,
v9.2.7 (Yes, I know, it's old. Nothing I can do about it.)
During a "whole database" restore using pg_restore of a custom dump, when is
the data actually loaded? I've looked in the list output and don't see any
"load" statements.
Thanks
--
World Peace Through Nuclear Pacification
Hi,
How is this done in v8.4?
postgres=# SELECT datname, datfrozenxid, age(datfrozenxid)
postgres-# FROM pg_database;
datname | datfrozenxid | age
---+--+---
template1 | 3603334165 | 25735089
template0 | 3603470462 | 25598792
postgres | 3576970250 | 52
On 10/29/2017 03:37 PM, David G. Johnston wrote:
On Sunday, October 29, 2017, Ron Johnson <mailto:ron.l.john...@cox.net>> wrote:
Hi,
v8.4.17
http://www.postgresql-archive.org/pg-clog-questions-td2080911.html
<http://www.postgresql-archive.org/pg-clog-questions-td
Hi,
v8.4.17
http://www.postgresql-archive.org/pg-clog-questions-td2080911.html
According to this old thread, doing a VACUUM on every table in the
postgres, template1 and TAPd databases should remove old pg_clog files.
postgres=# SELECT datname, age(datfrozenxid) FROM pg_database;
datname
On 10/18/2017 10:16 AM, Igal @ Lucee.org wrote:
On 10/18/2017 7:45 AM, Ron Johnson wrote:
On 10/18/2017 09:34 AM, Igal @ Lucee.org wrote:
A bit off-topic here, but why upgrade to 9.6 when you can upgrade to 10.0?
There's no way we're going to put an x.0.0 version into producti
On 10/18/2017 09:34 AM, Igal @ Lucee.org wrote:
On 10/18/2017 6:24 AM, Ron Johnson wrote:
On 10/17/2017 11:17 AM, Tom Lane wrote:
Ron Johnson writes:
Where can I look to see (roughly) how much more RAM/CPU/disk needed when
moving from 8.4 and 9.2?
It's entirely possible you'll
On 10/17/2017 11:17 AM, Tom Lane wrote:
Ron Johnson writes:
Where can I look to see (roughly) how much more RAM/CPU/disk needed when
moving from 8.4 and 9.2?
It's entirely possible you'll need *less*, as you'll be absorbing the
benefit of several years' worth of performanc
Where can I look to see (roughly) how much more RAM/CPU/disk needed when
moving from 8.4 and 9.2?
Thanks
--
World Peace Through Nuclear Pacification
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/
On 10/09/2017 01:02 PM, Scott Mead wrote:
On Mon, Oct 9, 2017 at 1:19 PM, Ron Johnson <mailto:ron.l.john...@cox.net>> wrote:
Maybe my original question wasn't clear, so I'll try again: is it safe
to do a physical using cp (as opposed to rsync)?
Yes -- however*you
Maybe my original question wasn't clear, so I'll try again: is it safe to do
a physical using cp (as opposed to rsync)?
On 10/09/2017 11:49 AM, Darren Douglas wrote:
Ron:
Here is an explanation that may help a bit.
Your script is executing a PHYSICAL backup. A physical backup i
On 10/09/2017 11:33 AM, Jeff Janes wrote:
On Mon, Oct 9, 2017 at 6:40 AM, Ron Johnson <mailto:ron.l.john...@cox.net>> wrote:
Hi,
v8.4.20
This is what the current backup script uses:
/usr/bin/psql -U postgres -c "SELECT
pg_start_backup('Incrementalbackup
TX 78665-2106
*From: * on behalf of Ron Johnson
*Date: *Monday, October 9, 2017 at 8:41 AM
*To: *"pgsql-general@postgresql.org"
*Subject: *[GENERAL] Using cp to back up a database?
Hi,
v8.4.20
This is what the current backup script uses:
/usr/bin/psql -U postgres -c "SELECT
Hi,
v8.4.20
This is what the current backup script uses:
/usr/bin/psql -U postgres -c "SELECT pg_start_backup('Incrementalbackup',true);"
cp -r /var/lib/pgsql/data/* $dumpdir/data/
/usr/bin/psql -U postgres template1 -c "SELECT pg_stop_backup();"
Should it use rsync or pg_dump instead?
Thank
On 09/20/2017 01:05 PM, Jerry Sievers wrote:
Ron Johnson writes:
On 09/19/2017 05:00 PM, Jerry Sievers wrote:
[snip]
The DB is 10TB total size with OLTP plus some occasional heavy batching
which frequently correlates with degradation that requires intervention.
Unrelated server problem
On 09/19/2017 05:00 PM, Jerry Sievers wrote:
[snip]
The DB is 10TB total size with OLTP plus some occasional heavy batching
which frequently correlates with degradation that requires intervention.
Unrelated server problem forced us to relocate from a Debian/Wheezy 3.x
kernel 1T 144 CPU to the ev
On 09/18/2017 08:17 AM, Melvin Davidson wrote:
[snip]
I don't have any specific suggestion for an additional column, other than
Berend's idea. However, I strongly advise against the use
of ENUM's. They can create a major problem in the event one needs to be
removed.
Because it will internally
On 09/15/2017 06:34 AM, Justin Pryzby wrote:
[snip]
But you might consider: 1) looping around tables/indices rather than "REINDEX
DATABASE", and then setting a statement_timeout=9s for each REINDEX statement;
Is there a way to do that within psql? (Doing it from bash is trivial, but
I'd rathe
On 09/07/2017 09:32 AM, Tom Lane wrote:
Ron Johnson writes:
On 09/07/2017 09:08 AM, Tom Lane wrote:
Manual cleanup shouldn't be very hard, fortunately. Run pg_controldata
to see where the last checkpoint is, and delete WAL files whose names
indicate they are before that (but not th
On 09/12/2017 01:45 AM, Frank Millman wrote:
Hi all
I am using 9.4.4 on Fedora 22.
I am experimenting with optimising a SQL statement. One version uses 4
LEFT JOIN’s and a 5-way CASE statement in the body. The second moves the
filtering into the JOIN section, and I end up with 16 LEFT JOIN’s an
Hi,
v 9.2.7
Based on LENGTH(offending_column), none of the values are more than 144
bytes in this 44.2M row table. Even though VARCHAR is, by definition,
variable length, are there any internal design issues which would make
things more efficient if it were dropped to, for example, VARCHAR(2
On 09/07/2017 05:07 PM, Michael Paquier wrote:
On Thu, Sep 7, 2017 at 11:08 PM, Tom Lane wrote:
Manual cleanup shouldn't be very hard, fortunately. Run pg_controldata
to see where the last checkpoint is, and delete WAL files whose names
indicate they are before that (but not the one including
On 09/07/2017 09:08 AM, Tom Lane wrote:
Ron Johnson writes:
After disabling log shipping via setting "archive_mode = off", and then
running, "pg_ctl reload", old WAL files and their associated .ready files
aren't being deleted.
Hmm. I might be misremembering,
Hi,
v8.4 (and there's nothing I can do about it).
After disabling log shipping via setting "archive_mode = off", and then
running, "pg_ctl reload", old WAL files and their associated .ready files
aren't being deleted.
Is there any document you can point me to as to why this is happening, and
On 08/30/2017 08:48 AM, Scott Mead wrote:
On Wed, Aug 30, 2017 at 9:43 AM, Ron Johnson <mailto:ron.l.john...@cox.net>> wrote:
Hi,
For any of you with those failover clusters, do you know if "pg_ctl
reload" works (for compatible config file changes), or mus
Hi,
For any of you with those failover clusters, do you know if "pg_ctl reload"
works (for compatible config file changes), or must we bounce the database
using "hares -offline" then "hares -online"?
Thanks
--
World Peace Through Nuclear Pacification
--
Sent via pgsql-general mailing list
On 08/28/2017 08:22 AM, Stephen Frost wrote:
* Christoph Moench-Tegeder (c...@burggraben.net) wrote:
## Ron Johnson (ron.l.john...@cox.net):
How is this done in v8.4? (I tried adding "date; rsync ..." but pg
didn't like that *at all*.)
There's a DEBUG1-level log m
On 08/28/2017 06:06 AM, Christoph Moench-Tegeder wrote:
## Ron Johnson (ron.l.john...@cox.net):
How is this done in v8.4? (I tried adding "date; rsync ..." but pg
didn't like that *at all*.)
There's a DEBUG1-level log message on successful archive_command
completion - t
Hi,
How is this done in v8.4? (I tried adding "date; rsync ..." but pg didn't
like that *at all*.)
Thanks
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 08/27/2017 02:23 PM, Christoph Moench-Tegeder wrote:
## Ron Johnson (ron.l.john...@cox.net):
Everything I've read says that you should use "rsync -a". Is there
any reason why we can't/shouldn't use "rsync -az" so as to reduce
transfer time?
On to
Hi,
(Yes, its old. Nothing I can do about that.)
Everything I've read says that you should use "rsync -a". Is there any
reason why we can't/shouldn't use "rsync -az" so as to reduce transfer time?
Also, does that change require a full restart (difficult with production
systems)?
Thanks
On 08/22/2017 02:55 PM, Joshua D. Drake wrote:
On 08/22/2017 12:48 PM, rakeshkumar464 wrote:
We have a requirement to encrypt the entire database. What is the best tool
to accomplish this. Our primary goal is that it should be transparent to the
application, with no change in the application, a
On 08/11/2017 02:35 PM, Peter Eisentraut wrote:
On 8/11/17 10:15, Murtuza Zabuawala wrote:
some time whe have 2 process postgres for 1 instance like this
exppgs*17769* 1 0 01:06 ?00:01:04
/usr/pgsql-9.3/bin/postgres -D /bases/postgresql/scl/data -i -p 5450 -h
bd-sillage.info.
ogh כתב:På onsdag 10. mai 2017 kl. 16:55:50, skrev Ron Ben <ronb...@walla.co.il>:
I think you miss understood me.
pg_dump dumps the data. the tables, functions and the data saved in them.
I have daily backups for this so i'm not worried.
What i'm woried about are the "ex
er כתב:On 05/10/2017 06:08 AM, Ron Ben wrote:> I'm about to upgrade my postgresql to the latest 9.3 version> On my test server eveything works.> However I want to save a backup of my production server before the > upgrade...> I'm not sure how I do that.https://www.postgresq
I'm about to upgrade my postgresql to the latest 9.3 version
On my test server eveything works.
However I want to save a backup of my production server before the upgrade...
I'm not sure how I do that.
It says that only system files are changed during upgrade... which folders exactly I need to
hich is not always the case. And as mentioned earlier 9.3.5 and 9.3.9 can create problems as they require specific checks.
I'd appriciate any insight.
× ×פר׳ 26, 2017 13:26, Sameer Kumar ×ת×:
On Wed, Apr 26, 2017 at 4:41 PM Ron Ben <ronb...@walla.co.il> wrote:
I'm runing PostgreSQL 9.3.3 and I want to upgrade it to the latest 9.3 version
The documontation does not specify what needs to be done other than "just install the executables".
This is wierd as for example 9.3.5 release notes request to run a specifc query to check for pg_multixact files left.
ton כתב:On Sat, Apr 22, 2017 at 12:04 PM, Ron Ben <ronb...@walla.co.il> wrote:Why to use mailining list rather than forum?
forum gives much more flexablitiy, easy to read and respond, allows to search for other simillar issues, topics can be tagged...
Was this intended to display irony re: &
Why to use mailining list rather than forum?
forum gives much more flexablitiy, easy to read and respond, allows to search for other simillar issues, topics can be tagged...
But if you add another GRANT statment to user it won't be in the last.. you have no way of knowing the correct order of GRANTS.
ב אפר׳ 19, 2017 17:26, Adrian Klaver כתב:On 04/19/2017 07:16 AM, Ron Ben wrote:> Here :)Thanks.See my previous response. Basically we need more information bef
Adrian Klaver כתב:On 04/19/2017 06:49 AM, Ron Ben wrote:Is it possible to get your email program to left justify text on sending? I can figure out the right justified text, it just takes me longer.> I think I may have found the problem.>> The role defined as:>> CREATE ROLE &quo
ake the last known command of grant?
Sadly, when there are more than one role it's impossible to know which role was first. PostgreSQL shows them alphabeticly rather than by date so in case of overlaping instructions its impossible to know which one was first.ב אפר׳ 19, 2017 16:40, Adrian Kl
Hi,
I'm using PostgreSQL 9.3.2
I'm running the command:
psql -h testserver -U ronb -f backup.sql -q -d foldertest 2>error.txt >output.txt
This should generate my database in foldertest
However this doesn't work. It's unable to create schemas
in the error.txt i see "permission denied for databa
Hi,
I know I can solve my issue localy but I think that percentage manipulation is commonly used by many users and while it's true that each one can create his own solution localy it would be nice if postgresql would have build in functions for that.
percentagee manipulation is a core fuctionalit
Hi,
I'm always finiding myself writing many varations of functions to calculate percentage.
I think it would be nice if postgresql would have build in functions for that.
I think the major functionality is something like the 3 ooptions here:
https://percentagecalculator.net/
It may help to keep c
eople will find usefull and it doesn't seem like a lot of work to implement it.ב מרץ 28, 2017 19:42, David G. Johnston כתב:On Tue, Mar 28, 2017 at 7:09 AM, Adrian Klaver <adrian.kla...@aklaver.com> wrote:On 03/28/2017 12:29 AM, Ron Ben wrote:
Here is a refer to the stackoverflow question:
Hi,
position(substring in string)
as listed here:
https://www.postgresql.org/docs/9.1/static/functions-string.html
locates sub string in a string.
It doesn't support locateing the substring from the back.
For example:
position('om' in 'Tomomas')
gives 2
But if I want to locate the first oc
pick your brains on this a
little.
Cheers,
Ron
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
s time taken for a search query.
What would be the best approach to this if I were to do this in the
database only? Should/can this be done with postgresql only or should I
look into other types of technology? (Lucene? Sphinx? others?)
Any advice on this would be greatly appreciated.
Thx in
minute.
Regards,
rs
-Original Message-
From: David Johnston [mailto:pol...@yahoo.com]
Sent: Tuesday, January 10, 2012 9:34 AM
To: Ron Somaraju; 'Tom Lane'
Cc: 'Scott Marlowe'; pgsql-general@postgresql.org
Subject: RE: [GENERAL] How do you change the size of the WAL fi
Once again, pros and cons should be left to users discretion because one may
have latest and greatest hardware and network resources. For example a SSD on a
fiber channel on a high speed network.
Regards,
rs
On Jan 9, 2012, at 7:06 PM, "Tom Lane" wrote:
> Scott Marlowe writes:
>> On Mon, Ja
abase, and recreating rules got it working. Dunno.
-Ron-
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
2011-09-05_16:14:00-0400 Tom Lane :
> Ron Peterson writes:
> > I just dropped my logging rules, stopped the database and restarted it,
> > put my rules back in place, and now it works. Not sure why. Cached
> > query plan?
>
> Maybe. We'd need a reproducible tes
2011-09-05_15:03:00-0400 Tom Lane :
> Ron Peterson writes:
> > I just updated a table to have a larger column size as follows.
>
> > alter table attributes_log alter column attribute_name type varchar(48);
>
> How come this refers to "attributes_log" while y
racter varying(24)
I'm using PostgreSQL 9.0.4
I tried to replicate this with a new database and a simple table, but
could not.
I had to drop (and then recreate) three rules and a view on this table
before altering the column.
This is a production database, so I need to treat it gently.
--
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
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
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
ok had 1800 MySQL servers with 2 DBAs.[1]
I wonder how that compares with large-scale Postgres deployments.
Ron
[1] http://perspectives.mvdirona.com/2008/04/22/1800MySQLServersWithTwoDBAs.aspx
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your s
any vendors offering engines?
[ 1/2 :-) ]
Ron
[1]
http://www.computerworld.com/s/article/9087918/Size_matters_Yahoo_claims_2_petabyte_database_is_world_s_biggest_busiest
"Yahoo brought the database in-house and continued to enhance
it, including tighter data compression, more parallel data
proce
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
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
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
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
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
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
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
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
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.
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:
>> 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
>
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
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:
::=
[ ] { | }
...
::=
|
::=
[ [
[ ] ] ]
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
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');
>
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%
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
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
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:
> 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
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
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
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 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
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.
>
>
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
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.
*
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
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
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
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 ..
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
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
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
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
1 - 100 of 990 matches
Mail list logo
