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
al small databases. And, if for any reason
the backup needs to be human-readable, this is the approach of choice as well.
Darren
The first
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 sc
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.
15K SCSI drives
will override any possible Opteron CPU fan quietness.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHVNgCS9HxQb37XmcRArgLAKCqTxy49KKaRy3P2UUqEyy6LJJKHACg0RDm
8T
ail, but instead of
> creating a separate table for every user, you could use one table ,
> partitioned on userid, that would , however, add a maint overhead whenever
> you add a new user.
Cluster by *range* of user ids, and preallocate some number of
tablespaces.
- --
Ron Johnson, Jr
ta)
>
> 2. example (a big number of tables)
> tablename_user_id( id, datetime, some_data)
This should help you to decide how to design your tables. 3NF is as
far as you really need to go.
http://en.wikipedia.org/wiki/Data_normalization
http://pubs.logicalexpressions.com/Pub0009/LPMArticl
y bad english:( )
Bed English? You should see my Russian!!!
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHUvf5S9HxQb37XmcRApraAKDlKLorRwSSuqVe66cUBbmPdaJXrQCgsLa0
589HllNDuKk8ImByzPA
ting on a tiny database.
Is the SP written as efficiently? (Think of ways to refactor it in
order to get the same results with less effort.)
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Lin
r databases are too big for single-
threaded backups. The proprietary backup scheme is transactionaly
consistent and format lets us easily restore to systems with wildly
different disk layouts than the original database.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraf
list the field names your code is expecting.
> Besides, I don't think you can do what you want to do with just SQL.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTaTaS9HxQb37Xm
x27;t optimized for having 100+ processes reading and writing to the
> same file. Probably others..
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTaP3S9HxQb37XmcRAoFfAJ4gQJI
serious UNIXes like Solaris.
Wasn't there a time (2 years ago?) when PG ran pretty dog-like on SPARC?
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTMzQS9HxQb37XmcRAo91AJ0d1l1LW0RE
ok from NeXT was the GUI design and object oriented application framework
> stuff. Basically all the stuff that Unix programmers still haven't quite
> figured out what it's good for.
Even AfterStep is written is plain C...
- --
Ron Johnson, Jr.
Jefferson L
0
scaled *better* than Linux 2.6 after 4 CPUs.
http://jeffr-tech.livejournal.com/5705.html
Turns out that there was/is a bug in glibc's malloc(). Don't know
if it's been fixed yet.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is f
w many
northeasterners don't know what state their vehicle is registered in.)
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHSzxlS9HxQb37XmcRAh0QAKCLp5aNkoPPs8P5oXQCJ0HI
single part failure will
knock out both directory structures.
> Alex
>
> On Nov 24, 2007 12:06 PM, Steve Atkins < [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>
> On Nov 24, 2007, at 8:17 AM, Ron Johnson wrote:
>
> > -BEGIN PGP SI
gt; buying more drives and a good RAID controller if I needed more
> performance.
Remember: disks are *cheap*. Spend an extra US$250 and buy a couple
of 500GB drives for RAID 1. You don't mention what OS you'll use,
but if you really need cheap then XP & Linux do sw RAID,
ingle fields if they need
> to be referenced but should also be natural if at all possible. ie use
> car number plates rather than some serial int.
I wouldn't trust plate number to be unique over time, since the
format "ABC 123" only has a capacity of 17,576,000 vehicles.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/07 01:21, Gregory Stark wrote:
> "Ron Johnson" <[EMAIL PROTECTED]> writes:
>
>> On 11/16/07 12:50, João Paulo Zavanela wrote:
>>> Hello,
>>>
>>> How many fields is recomended to crea
only stubborn fools won't
admit that they can't divine all situations. So, you add a new
column to the PK and keep on going.
But still, there *are* some circumstances where natural PKs just
don't work. After all, SSNs and credit card numbers are synthetic
(just not generated sequen
ed
for uniqueness. 1 or 6 or 24. Doesn't matter.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHPej/S9HxQb37XmcRAo5mAJoDwp1E+aL2M/oTWhOsR5XYJi0AhgCgvUgU
/ZB7nP+K6j0WW8vNn5Q8t
7;d be tempted to stay
> away from primary keys of more than a single column.
Fie on you evil synthetic key lovers. Long live the Natural Key!
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GN
f us prefer it.
> But they could just adhere to the "law of the land", or "when in
> Rome, ... " practice instead of kicking off fuss. And with my
> "mail client" top-posting has no place. Let's just stick to good
> old standards.
What ever ha
hink got answered was how to
> undo an "initdb". "dropdb" drops a DB, but how do I undo an "initdb"?
>
>
> -dave
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/07 09:58, Tom Lane wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
>> On 11/07/07 09:03, Gauthier, Dave wrote:
>>> Is there such a thing as a temporary, probably in-memory, version of a
>>> Postgres DB?
>
7;s not exactly what you're talking about, but I think
it's as close as you'll get.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD
ng_column);
>
> All in the manuals:
> http://www.postgresql.org/docs/8.2/static/sql-altertable.html
>
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNAT
it appears that one needs to be root to execute these statements.
>
> Is there any other way for non-root users?
The whole idea of enforcing Relational Integrity in the database
engine is to *not* allow "regular users" to bypass data integrity
checks.
- --
Ron Johnson, Jr.
Jeffers
l.org/docs/8.2/interactive/sql-altertable.html
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHIbwhS9HxQb37XmcRAjg6AJ4sPW7wPH599JPVdmZ5s2
e/Compact. But I see this as limiting use to only
> features supported by the Compact edition, or having to install SQL Express
> - which I can see as being worst than supporting Postgres Installs.
I think that you're just going to have to create a pilot project to
see how it fits your i
ess test even if you know it's useless.
Not to bash MySQL (much...) but ISTM that this is another example of
MySQL playing fast and loose with SQL.
IOW, the RDBMS shouldn't try to out-think me even if I seem seem to
be doing something odd.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a ma
ny):
>> BLOB - Binary Large Object
>
> Do we use that term? Normally for us it's "large objects".
Good news everyone! "Large objects" is generic enough that if PG is
ever ported to the IBM 1400 that you won't have to come up with a
new acronym: DLOB (Decimal L
Select one, two, three, four, five, six, seven from loop_import
>order by loop_id ;
> fetch next From loop_set;
Wouldn't it be simpler to do:
INSERT INTO some_temp SELECT field list FROM some_table;
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats f
for
> long time, and since we dont log all queries it is next to impossible to
> tell where in app code the problem lies.
> it would be very useful to get something like "previous query".
Transaction analysis is the way to go here. It requires a serious
code review, though.
>
ing execution
>> of the first SELECT
>
> Within a single *transaction*. If you run the above SELECT again, it
> will see the newly added row.
And this is the big difference between READ COMMITTED and
SERIALIZABLE. With the latter, inside a single transaction the same
query will ret
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/07 11:06, Geoffrey wrote:
> Ron Johnson wrote:
>>
>> On 10/04/07 10:28, Geoffrey wrote:
>>> Anyone have a recommendation for a good sql tutorial? Looking for a
>>> book, but online would be useful as well
sql in order to generate reports with a report writer like openrpt.
>
> Thanks for any suggestions.
My suggestion: tell him that the SQL interface is "broken".
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for
able to convert a PostgreSQL database to other formats
>>>> such as Oracle, Access etc. - with, as well as without, the data.
>>>>
>>>> Can this task be accomplished by employing pg_dump in SQL?
>
> If you dump with inserts, data only, then yes but it will be s
asily.
How difficult is it to specify tablespace when creating an index?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE-
Versi
On 09/30/07 10:31, brian wrote:
[snip]
>
> The default for MySQL is latin1 with swedish sorting.
Yorn desh born, der ritt de gitt der gue
Orn desh, dee born desh, de umn børk! børk! børk!
--
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fis
> Which initdb has done since 8.0. If the OP is such a rabid UTF8 fan,
> one wonders why his default locale setting isn't using UTF8 ...
He uses Windows?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/23/07 22:40, Ow Mun Heng wrote:
> On Thu, 2007-09-20 at 07:55 -0500, Ron Johnson wrote:
>> On 09/20/07 05:43, Ow Mun Heng wrote:
>
>>> hehe.. I'll end up running it on a low-end desktop w/ 1GB ram and a
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/20/07 05:43, Ow Mun Heng wrote:
> On Wed, 2007-09-19 at 08:40 -0500, Ron Johnson wrote:
>>> Yes, I think that it's a bit excessive but the company can afford it so why
>>> not... :)
>> Lucky SOB.
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/19/07 08:32, Bjørn T Johansen wrote:
> On Wed, 19 Sep 2007 07:59:36 -0500
> Ron Johnson <[EMAIL PROTECTED]> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 09/19/07 07:33, Bjørn T Jo
supported under Linux (not heard
> of it before...)
Google says "yes".
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8D
is a java
> app, and we need need something that can run java fast as well as
> postgresql...
12-14 users on a Quad-core system with 4GB RAM?
Am I so old that (even accepting Tomcat and Java) that seems
"excessive"?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, a
AS NUMERIC(8,2)) AS FIST_SELF_SUFFICIENCY
FROM T_REGION R,
T_COUNTRY C,
T_NATIONAL_STATISTICS NS
WHERE R.REGION_ID = 'WESTAFRI'
AND C.REGION_ID = R.REGION_ID
AND NS.COUNTRY_ID = C.COUNTRY_ID;
You might want to left outer-join NS to C to indicate any west
African countries with mi
t; min/max/average/count/stdev of the weekly sample size based on different
> products/software mix etc.
>
> and still be able to answer correctly, what's the average of data_1 over
> the pass 2 months?
That's the purpose of data warehouses and ETL, isn't it?
- --
Ron
Exchange server
to your local box. But, as another poster mentioned, you still have
to be attached to an Exchange domain for it to work.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/15/07 19:59, Panagiwths Pediadiths wrote:
>
> On Sat, 15 Sep 2007, Ron Johnson wrote:
>
> On 09/15/07 03:28, Panagiwths Pediadiths wrote:
>>>> Thats the fun part, I actually need to allow duplicates in specific cases
urrent_time as time));
> date_part
> --
> 60030.824587
> (1 row)
>
>
> Isn't current_time already a time? Why is the cast necessary?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
In the context of one transaction i do many queries of the form
>>> INSERT INTO table value WHERE value NOT IN TABLE;
>>>
>>> If i have 2 processes running the same 100s of these at the same time i
>>> end up with duplicates.
>>> Even with iso
vant 10 years ago, is it
really necessary in 2007? A couple of MSA-1000s stuffed with 1TB
disks would hold an l-o-t *lot* of historical data.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE---
quot;value is NULL". A
left outer join would handle that.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG57E/S9HxQb37XmcRAsb/AJ97lFt25sLwIYhkhQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/07 12:02, Phoenix Kiula wrote:
> On 12/09/2007, Ron Johnson <[EMAIL PROTECTED]> wrote:
>> How (on average) large are the records you need to insert, and how
>> evenly spread across the 24 hour day do the inserts occur?
houghts based
> on above info.
How (on average) large are the records you need to insert, and how
evenly spread across the 24 hour day do the inserts occur?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-
rmance
> across a single-CPU Quad Core Xeon with a dual CPU dual-core AMD
> Opteron? Or should the hard disk and RAM be the major considerations
> as usually proposed?
Opteron is the standard answer.
What is your backup/recovery strategy?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/10/07 19:50, Tom Lane wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
>> On 09/10/07 15:21, Alvaro Herrera wrote:
>>> I wouldn't trust the browser's TZ, and you would need a way to
>>> override it.
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/10/07 15:21, Alvaro Herrera wrote:
[snip]
>
> I wouldn't trust the browser's TZ, and you would need a way to
> override it.
Why?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him
pick one if you get it wrong. Then you can store that
> timezone in a user profile and set it everytime the user uses your web
> app.
In both Windows *and* Unix "you" set your TZ when you install the
system. There are system functions to inquire how you've set it.
Brows
really like to avoid doing that.
Why?
The (literally) cardinal rule of database normalization is
"eliminate repeating values".
> Is there a solution to this problem with arrays of foreign keys, and
> if so, how does one do that?
>
> Thanks for any help.
- --
Ro
internal clocks set to UTC for a decade
or more, and there have been no noticeable ill effects, since apps
all know to adjust for TZ.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-BEGI
to a
*separate* database (so that backups & CREATE INDEX don't clash),
indexes them perfectly for this query, and then runs the query
against this separate database.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/07 09:00, Ow Mun Heng wrote:
>
>>Datahouse or "data warehouse"?
>
> OLTP data warehouse.
But OLTP & DW are diametrically opposed in how you design,
structure, load and use them.
- --
Ron Johnson, Jr.
Jeffers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/07 07:49, Merlin Moncure wrote:
> On 9/7/07, Ron Johnson <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 09/06/07 20:53, Merlin Moncure wrote:
>> [snip]
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/07 01:37, Greg Smith wrote:
> On Fri, 7 Sep 2007, Ron Johnson wrote:
>
>> Definitely a niche product.
>
> Stonebraker's commentary was unfortunately spun by the ComputerWorld
> columnist.
Tech journalist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/07 02:49, Ow Mun Heng wrote:
> On Fri, 2007-09-07 at 00:18 -0500, Ron Johnson wrote:
>> On 09/06/07 21:26, Ow Mun Heng wrote:
>> I've not arrived at any conclusion but merely
>>> exploring my options on which wa
ything to do with the concept of a relational
> database. It's an implementation detail --- maybe a pretty fundamental
> one, but in principle you could build a DB either way and no user could
> see a semantic difference.
- --
Ron Johnson, J
1 - 100 of 637 matches
Mail list logo
