performance
takes a big hit. But it definitely works...
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You know, I'd have sworn that I changed "extra 4" to "extra 9"
Sorry.
On 10/10/06 12:49, Alex Turner wrote:
> Awesome - thank you!
>
> Alex
>
> On 10/9/06, *Ron Johnson* <[EMAIL PROTECTED]
> <mail
"ON UPDATE CASCASE" then you are fine.
>
> Just updated the main table and PostgreSQL will take care of the rest.
I doesn't appear that ALTER TABLE can change constraint characteristics.
You'd have to drop/recreate, no?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "
with only 6MB RAM. Supported *70* online users and had a
*relational* database (CA Datacom-DB).
Of course, the FEPs, block-mode terminals and CICS were the crucial
difference.
Damned shame that Unix killed that mentality, and that client-server
was usually implemented so poorly.
- --
Ron Johns
; Here I what I came up with:
>
[snip]
>
>
> It is nice to see things work so well. :-)
It would be interesting to see how well it works on a 50M row table.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense&qu
nly small fraction of the 50 M rows
> would be affected and hopefully updating primary keys isn't a
> common occurrence.
I was thinking of the ALTER TABLE ... ADD CONSTRAINT column.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/06 19:10, Geoffrey wrote:
> Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 10/11/06 14:48, Chris Browne wrote:
>>> [EMAIL PROTECTED] (Andrew Sullivan) writes:
>>>&g
es, regardless of
whether partitioning or a "viewed UNION ALL", which will the query
optimizer and constraint_exclusion be more friendly towards?
Thanks,
Ron
--
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to whit
you aggregate, join and WHERE it.
As Tom notes, other RDBMSs do pre-query optimizations. SET TRANS
READ ONLY tells the engine that these statements won't have to take
out concurrent write locks, and can thus take a different, faster
code path.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "comm
> Don't bother. I already typed it in and have it on cassette tape here
> somewhere. I'll send it via parcel post with two 13 cent stamps as soon
> as I finish watching War Games on my betamax.
>
> Is Carter still president?
No, Reagan is. WG was released in 1983 and th
in tightly in the pages, and
the pages are close together", so the optimizer could decide "a
table scan would be much more efficient".
In some ways, this would be similar in functionality to the existing
histogram created by ANALYZE, but would provide a slightly different
picture.
ql.org|80.179.151.210|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/html]
[ <=> ] 0
- --.--K/s
21:45:10 (0.00 B/s) - `index.html' saved [0/0]
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" re
p postgres, and *is* able to create files in that
directory.
File /var/log/postgresql/postgresql-8.1-main.log gives the same
error that psql does, and there's nothing in syslog.
Any help appreciated.
--
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/06 03:51, Sandeep Kumar Jakkaraju wrote:
> Can we convert from Postgres to Oracle !!???
Are you asking permission?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sen
or am I missing something?
Also, how do you calculate the size of a NUMERIC?
Lastly, I know they are the same, but which is the
"preferred/standard" type: NUMERIC or DECIMAL?
Thanks
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/06 22:14, Michael Glaesemann wrote:
>
> On Oct 18, 2006, at 9:46 AM, Ron Johnson wrote:
>
>> SMALLINT(2)
>> INTEGER(2)
>> BIGINT(2)
>
>> Are these data-types not in PG, or am I missing somethin
> I tested binary quite a bit and only found it to be a win if moving
> blobs in and out of the database. On 'normal' tables of mixed fields
> types of small size, it can actually be slower. Binary is a bit
> faster for native types and bytea, and slower for character
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/06 09:47, Merlin Moncure wrote:
> On 10/18/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
>> > I tested binary quite a bit and only found it to be a win if moving
>> > blobs in and out of the database. On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/06 14:08, [EMAIL PROTECTED] wrote:
> Is there any command to drop all the database at once>
> drop database dbname
> drops the individual database.
> I am using ver8.1
> thanks,
DROP DATABASE ;
- --
Ron Johnson, Jr.
Jef
get for 8.2?
(If I get approval and the money, we'll be creating a roughly 8TB
database, and in-place upgrade is the only way that we'd be able to
migrate from $EXISTING_VERSION to $NEW_VERSION.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/06 17:22, Jim C. Nasby wrote:
> On Wed, Oct 18, 2006 at 04:27:21PM -0500, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 10/18/06 16:08, Jim C. Nasby wrote:
>>> On Mon, Oct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/06 17:56, Jim C. Nasby wrote:
> On Wed, Oct 18, 2006 at 05:42:22PM -0500, Ron Johnson wrote:
>>> In any case, you'll be much, much happier if you do this project on at
>>> least 8.1.x, as 7.4 is pretty long in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/06 18:08, Tom Lane wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
>> We'll be using RHES4, I guess, so if it uses 7.4, then I'll have to
>> convince the SysAdmin to install 8.1 or 8.2.
>
>
> Red
essage from server: ERROR: could not open relation
> 1663/18392/18400: No such file or directory
> pg_dump: The command was: COPY public.file (vfs_id, vfs_type, vfs_path,
> vfs_name, vfs_modified, vfs_owner, vfs_data) TO stdout;
What happens when you fsck the relevant partitions?
- --
plate1=# create database web_database owner web_user;
> ERROR: could not write to file "base/16390/2682": No space left on device
> template1=# exit
> template1-# \q
>
> Any ideas what may be causing this to happen?
"No space left on device"
Maybe your disk is
the world so you could just let those people deal with this one.
Yabut, "Is Postgres good for ... many simulataneous connections" is
just s ambiguous.
Just a *little* hint of his volume needs and any sort of Google
search would have been welcome.
- --
Ron Johnson, Jr.
Jefferson LA US
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/06 23:52, Rick Gigger wrote:
> Rick Gigger wrote:
>> Ron Johnson wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 10/18/06 19:57, Rick Gigger wrote:
>>>> To ma
ill determine how much time and money it takes.
Or... are you asking if there are automated tools?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/06 00:46, Rick Gigger wrote:
> Ron Johnson wrote:
>>
>> On 10/18/06 23:52, Rick Gigger wrote:
>>> Rick Gigger wrote:
>>>> Ron Johnson wrote:
>>>>>
>>>>> On 10/18/06 19:57, Ric
AMP, if "lamp" is a meta-
package, then:
$ aptitude show lamp
$ sudo aptitude install
And file an RFP bug (does Ubuntu use reportbug?) asking for a lapp
meta-package.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "com
these are validly long-running updaters, you (the OP) will
have to think outside the box for techniques to break that million-
row UPDATE statement into short-time committable chunks.
"Canditate key" tables and PL/pgSQL or a scripting language are one
possibility.
- --
Ron Johnson, Jr.
J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/06 23:02, Joshua D. Drake wrote:
> On Thursday 06 July 2006 19:55, Ron Johnson wrote:
>> Being an HP/Compaq shop, I'm looking at an Opteron-and-SATA-based
>> DL145 G2 and an MSA20 SATA enclosure with a U320 interface to u
can be
> | started. Furthermore, SIGKILL kills the postmaster process without
> | letting it relay the signal to its subprocesses, so it will be
> | necessary to kill the individual subprocesses by hand as well.
> `
But it can't be fatal, can it? After all, that's wha
ra performance right now.
>
> Are the differences between 8.1.5 and 8.2 significant? Is 8.2 more about
> speed or new features?
8.2 is not released yet. Can you risk your app on beta software?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example,
linking and "socket
conversations" are *not* linking in the GPL2 meaning, but the FSF &
RMS think differently. The GPL3 seems to codify that strictness.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense"
built the infrastructure and have (Oracle) DBAs to handle
> tuning, HA and so on.
Exactly. If you've already ponied up the big bucks for an Oracle
site license, why add extra complexity?
> Adding postgresql into that mix is a hard sell. Enterprise software
> that can support both po
ng about in the attic...
> hopefully something will come of it some day.)
The generalized version of this issue (transaction totally fails on
any error) is extremely painful.
Most RDBMSs (well, ok, the other RDBMSs that *I* have worked with)
don't do that, and there's a lot of code w
er sentence.
>>> Can anyone offer any insight as to weather it's fact or FUD?
>>
>> It is 100% FUD.
>>
> What would be the incentive for OpenCRX spreading FUD about PostgreSQL?
> Does anyone know?
That implies malice. The people at OpenCRX apparently really
beli
extremely* IO
constrained.
So,
- - What OS?
- - What version of PG?
- - what kind of disk system does the DB live on?
- - How many controllers?
- - What kind of tape drive?
- - Is it on it's own SCSI controller?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really val
gt; Shivkumar
>
> On 10/27/06, Stefan Kaltenbrunner <[EMAIL PROTECTED]> wrote:
>>
>> Ron Johnson wrote:
>> > On 10/26/06 01:20, Chris wrote:
>> >>> Coder At Heart wrote:
>> >>>> Hi!
>> >>>>
[snip]
>>
>>
e form:
>
> INSERT INTO ...
> IF PK-ERROR THEN
> UPDATE
> END-IF.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that
On 10/27/06 05:10, Gurjeet Singh wrote:
> On 10/27/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
>
> That doesn't help at all during multi-table transactions
>
>
> What problem do you think you would face in multi-table scenario? I tried
> the following and it work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/27/06 06:48, Gurjeet Singh wrote:
> On 10/27/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
>>
>> Dueling examples. Attached are two examples of errors.
>
>
> I think you completely missed that I am recommending usin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/27/06 08:41, Alexander Staubo wrote:
> On Oct 27, 2006, at 14:56 , Ron Johnson wrote:
>
>>> I think you completely missed that I am recommending using '\set
>>> ON_ERROR_ROLLBACK on' in psql.
>>>
>&
gh tps rates.
I'd rather spend my money on enough system RAM to keep the active
portion of my DB in the OS cache.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and
probably been done much easier: I'd welcome a helpful
> hint so as I know next time. :)
Unix is chock full of streaming text manipulation tools. In this
case, awk, Perl or Python would work well.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For examp
d on the client code, I wish one day it
> can be achieved with a SQL Statament thanks again .
You can do it in PL/pgSQL.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superio
creating a new schema that "just" has views back to the
base tables you want to dump. Then pg_dump the schema.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to b
27;t need external action, to make it do some task?
That's turning the RDBMS into the job scheduler.
>> Take a look at http://pgfoundry.org/projects/pgjob/
I did.
> Latest File Releases
> Package Version DateNotes / Monitor Download
> This Project Has Not Re
//www.postgresql.org/files/documentation/books/aw_pgsql/hw_performance/node11.html
Is this still accurate 3.75 years later?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superio
; capability (sounds like you do), then you can do that to create the copy
> rather than shutting the database down.
How does SAN-snapshot ensure transactional consistency?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/15/06 14:28, Martijn van Oosterhout wrote:
> On Wed, Nov 15, 2006 at 01:41:47PM -0600, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 11/15/06 09:47, Jim Nasby wrote:
>>&g
, what if the WAL is not on the SAN? You'd have to shut down
pg anyway, in order to copy the WAL to a new directory, no?
Lastly: in order to do SAN splitting without risking your data,
wouldn't you have to configure the disks as RAID-15 (mirrored
RAID-5), since splitting a RAID10 would leave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/15/06 15:51, Martijn van Oosterhout wrote:
> On Wed, Nov 15, 2006 at 03:25:38PM -0600, Ron Johnson wrote:
>> However, what if the WAL is not on the SAN? You'd have to shut down
>> pg anyway, in order to copy the WAL to
nced without an explicit
>> empty argument list.
>
> current_time and the like are hardcoded in the grammar. You'd have to
> do the same for sysdate. It's not hard, but then I'd question the
> hassle of having to patch all the Postgres installations you'
lots women
keypunched form data into Mohawk key-to-tape machines, and check
digits, which are also in credit cards and SSNs, are a perfect way
to protect against typos.]
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense&quo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/06 10:49, Martijn van Oosterhout wrote:
> On Thu, Nov 23, 2006 at 10:23:55AM -0600, Ron Johnson wrote:
>> For those times when and that when numeric sequences *are* needed
>> (employee_id and account_number for example) they s
nd credit card numbers, for a
good reason.
> You will need to add the check digit on most (all?) output that is
> interpreted by humans. The software itself can just use the number
> itself (assuming you don't need to check the integrity of the software).
>
> If you store the num
g to change, is there any advantage to doing
>> this?
>> If there are many-to-many reference tables (like name-to-friends) is
>> this any different?
>>
>> I've seen this a lot, but I've always assumed that with the condition
>> that 'name' w
r the kind of work I find myself doing, it's rare that it would be
> more efficient to not have the artificial construct. But that doesn't
> mean one is always better than the other.
>
> On Nov 24, 2006, at 11:14 AM, Ron Johnson wrote:
>
> But that requires that you
tly
> unique. Yes, really, duplicates have been issued in the past.)
Hmm, you're right. Other kinds of important numbers have check
digits, though.
http://www.cs.nmsu.edu/~cssem/DickOct18.pdf
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/06 11:47, Scott Marlowe wrote:
> On Thu, 2006-11-23 at 10:23, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 11/22/06 20:23, carter ck wrote:
>>> Hi all,
>>>
>&g
he west" in the past 30 years
without being surrounded by them.
It's their blind use in *every* table which I take issue with, *most
especially* when they are the only unique key.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "com
e/time, then
every CPA in the country will descend on me with calculators
sharpened if I decide to update the SALE_DATE column.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superi
ing real data as your keys, you have write
> complex queries or code to "fix" your data when the supposedly
> unchangeable data changes.
>
> Anyway, I'm sure this is a huge argument, but that's my 0.2
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense"
e sales master table. In fact,
*both* companies have a synthetic key on their sales master tables.
OMG, conflicting/overlapping synthetic keys!
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power
Yes there are problems with the above, namely you will likely have more
> than one joshua drake.
Right, and then the question gets to: how do you create a "good"
user id? Many prefer serial types; I prefer something that is not a
monotonically incrementing scalar.
- --
Ron Johnson,
initial copy/dump takes, but not so much after that.
If you've got excess CPU capacity at night, I wonder if -Z1 or -Z2
would speed the backup since it reduces the amount of data written
to disk.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, i
es guarantees that credit card numbers will not get reused after
> years of inactivity?
>
> Yes, there are natural keys, and it's good to use them to identify things
> for humans. But I got bitten many times by using them as primary. Many
> things that "will not change, ever&q
is not localized on disk?
As for the Seq Scan, Alexander is correct. What is the point of
using an index if there are no aggregates or WHERE, ORDER BY, GROUP
BY, etc clauses?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense&qu
anks and I really appreciate all the helps I've gotten so far.
Is the index ASC or DESC?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with br
ou use cron to set up a backup script?
But, but, but, but... that's not GUI! It makes me need to learn
shell!!! :(
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to
'Female'::text)))
>
> I personally prefer the second, as it's self-documenting...is there
> any other/better way of doing it?
I've only ever seen a CHAR(1) restricted to 'M'/'F'.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense"
space.
>
> Raymond O'Donnell wrote:
>> Just wondering.how do list member represent gender when storing
>> details of people in a database?
>>
>> I've done it two ways:
>>
>> * A bool column, with the understanding that true/false represents
ally an ISO standard (ISO 5218) for representing gender with
> numeric values: 0 = Unknown, 1 = Male, 2 = Female, 9 = not specified
> (or N/A).
Well, I guess that's what I'll be using next time.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really va
ote:
[snip]
> You know, here in the US not that many years ago we had a Surgeon
> General who lost their job because she suggested that people "scratch
> their own itch" ;-)
She lost her job because she advocated schools teaching children how
to "scratch their own itch"
state
> 9 = Neuter - Not applicable
>
> Hmmm... Easy to write the various functions making this a new datatype...
Is TG a biological state or a social state?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white
d to save disk
> space. I can store it as a bytea and compress it manually (zlib level
> 1 compression gives about 50% savings), but is there a way to force
> pg's own compression before I resort to this?
What can be compressed? Trailing whitespace or repeating substrings?
- --
Ron Jo
) ON UPDATE CASCADE
Why do you have indexes on both LOGIN_ID *and* LOGIN_ID + COLLECT_TIME?
ISTM that you can drop the LOGIN_ID index.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
wh
only query, but it'll nearly always decide it's a bad
> idea.
Scanning segment-2 of a 2-segment index seems like it would be
faster than scanning the table, if for no other reason than
"locality of data": the index will be smaller than the table, so
scanning it looking for re
ure of b-tree indexes, though, the optimizer
*will* use n_traffic_login_id_collect_time when you say WHERE
LOGIN_ID = 5;
>> ISTM that you can drop the LOGIN_ID index.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense&q
ebian in part because the Debian
> community does a good job themselves... If you call MySQL and you
> have support we support you if you are running Debian (the same
> with Suse, RHEL, Fedora, Ubuntu and others)... someone in Sales
> was left with the wrong information"
Oh, darn!
-
strings is much higher than for
> integers, so it will be slower.
And comparing INT8 is more expensive on a 32-bit system.
Since TEXT is totally variable, is there a big difference in TEXT vs
CHAR(8)?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For exampl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/06 07:50, Martijn van Oosterhout wrote:
> On Fri, Dec 15, 2006 at 07:44:16AM -0600, Ron Johnson wrote:
>>> The difference in performence will be determined by the cost of
>>> comparison. The cost of comparing strings is
s using separate databases use more RAM than a
>> single database with a bunch of different tables?
Config files are global, so I doubt it.
>> Company is growing rapidly, so growth room is important...
Then go for Option 1.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common
; within the confines of your hardware itself.
"infinite scaling within the confines of your hardware"!
How is that accomplished?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
white
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/21/06 17:15, Joshua D. Drake wrote:
> On Thu, 2006-12-21 at 16:54 -0600, Ron Johnson wrote:
> On 12/21/06 16:41, Joshua D. Drake wrote:
[snip]
>>>>> This solution seems to have the same problems as using dynamic
>&g
, you can get a SAN and attach a whole lot of
>> disk space, but your mobo will only accept a certain number of DIMMs
>> and processors of certain designs. And when your growing mega
>> database maxes out your h/w, you're stuck.
>
> Define mega... Because you would n
5000!)
Please tell me, though, what's so controversial about saying that
CPU and RAM resources are finite?
Besides, since pg_dump is single-threaded, backing up a huge
database gets impossible. Federating the database allows multiple
pg_dumps to simultaneously dump data to multiple tape drives.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/22/06 01:22, Tom Lane wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
>> Besides, since pg_dump is single-threaded, backing up a huge
>> database gets impossible. Federating the database allows multiple
>> pg_dumps
= 96KBps.
Trivial for even the slowest home-designed hard disks.
Let's then take the CPU. A dual-core 2GHz Opteron has 4 gigacycles
per second. That gives a dedicated machine 1 megacycle to handle
each variable per second.
I certainly think that's achievable...
- --
Ron Johnson, Jr.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What about empty space freed up by VACUUM?
On 12/28/06 03:11, Shoaib Mir wrote:
> This should help you get the disk usage for a table:
>
> select pg_size_pretty(pg_relation_size('tablename'));
- --
Ron Johnson, Jr.
Jefferson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/07 00:34, Mark Harrison wrote:
> I have a cluster of CPUs generating thumbnails for
> a render farm. I would like to place thumbnail
> requests on a queue, and have the cluster of client
> dequeue the requests and process them.
>
> Of course
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/07 20:39, Tom Lane wrote:
> John Sales <[EMAIL PROTECTED]> writes:
>> By doing this, I'm hoping that the query optimizer is smart
>> enough to see that if a query comes in and requests only the
>> six columns (that are in the narrower table) t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/07 07:28, Chander Ganesan wrote:
> Ron Johnson wrote:
>>
>> On 01/08/07 20:39, Tom Lane wrote:
>>
>>> John Sales <[EMAIL PROTECTED]> writes:
>>>
>>>> By doing this, I'm hopin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/18/07 00:22, Michael Glaesemann wrote:
>
> On Jan 18, 2007, at 15:15 , Gene wrote:
>
>> My calculations for disk space based off some information i found
>> online are ( 8 + ( 2 bytes for every four digits) ) for numeric and (
>> 4 + number of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/18/07 17:22, Scott Ribe wrote:
>> But this won't work if one had a text column of dates in various
>> formats, right?
>
> Right. In my case I have bad data from a source I didn't control, exported
> via code that I do control which happens to ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/18/07 17:52, David Fetter wrote:
> On Thu, Jan 18, 2007 at 05:42:54PM -0600, Ron Johnson wrote:
>>
>> On 01/18/07 17:22, Scott Ribe wrote:
>>>> But this won't work if one had a text column of dates in various
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/18/07 18:29, Alan Hodgson wrote:
> On Thursday 18 January 2007 15:54, Steve Atkins <[EMAIL PROTECTED]> wrote:
>> Anyone else get spam from EnterpriseDB today, talking about
>> "Postgresql Support Services"?
>>
>
> yep. You really would think th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/07 11:51, Guy Fraser wrote:
> On Thu, 2007-01-18 at 17:48 -0800, Richard Troy wrote:
>> On Thu, 18 Jan 2007, Joshua D. Drake wrote:
[snip]
> I feel that all @en25.com and @enterprisedb.com should be
> considered for banning from the PostgreSQ
201 - 300 of 637 matches
Mail list logo
