-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 16:27, Glen Parker wrote:
Open-database file-level backups might work with PITR, but I
wouldn't trust it.
IME, it does work, and very well. Inconsistencies in the heap files are
trumped by the WAL archive during recovery.
Tarring
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 18:04, Glen Parker wrote:
Tarring hot database files still gives me the willies. But then, I
wear belt and suspenders.
I understand. A list of file changed while we read it errors is just
a little unnerving at first!
I did quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 19:02, Jim C. wrote:
I've a postgres statement that reads:
CREATE TABLE channel (
Do you *need* object names to be case-sensitive?
If not, it's a bad habit to get in to. Makes more work for you and
the developers.
chanid int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/07 21:31, RPK wrote:
How is FireBird rated when compared with PostgreSQL?
Rated?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFwrSGS9HxQb37XmcRAj+lAJ9uFM+hNm+ink5SeOaaNRjCuASMaACgiBeE
PmhLjdXNwlPKRHHYpGuK+c4=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 23:46, Paul Lambert wrote:
Richard Troy wrote:
[snip] My observation is that we have a real shortage of
quality
[snip]
Meanwhile, what Operating Systems ARE _today_ reliable choices
upon which to run your Postgres datababse engine?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/31/07 12:37, Jeff Davis wrote:
On Tue, 2007-01-30 at 20:44 -0800, David Fetter wrote:
On Tue, Jan 30, 2007 at 04:43:14PM -0800, Richard Troy wrote:
On Tue, 30 Jan 2007, Mark Walker wrote:
I don't know. My customers expect 24/7 reliability.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/31/07 20:00, Paul Lambert wrote:
Mark Walker wrote:
One other thing. Another approach to this problem would be to have
some sort of code signing/authentication capabilities for the
postgresql server. For instance, you login as an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 00:32, Hakan Kocaman wrote:
Hi,
you can find a nice virtual folder implementation in the
Opera-Mailclient M2. Not sure if this also works with IMAP (don't
use IMAP yet).
Virtual folders are based on regexes over various fields of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 13:33, Brandon Aiken wrote:
I always assumed the general argument is if you need to query different
databases on the same server with the same application, they ought not
to be separate databases because they're clearly related data.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 14:41, Tony Caduto wrote:
Mark Walker wrote:
It's sort of a matter of taste, but there are lots of people who like
to keep there logic on the server or at least within sql statements,
so there's probably a good sized market that your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 14:50, Rich Shepard wrote:
On Tue, 30 Jan 2007, Mark Walker wrote:
[snip]
At last year's at O'Reilly's OSCON here in Portland I had this discussion
with the booth babes sales droids from Sugar-CRM. They said that they heard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 15:55, Richard Troy wrote:
On 01/30/07 14:41, Tony Caduto wrote:
Mark Walker wrote:
[snip]
These days with good open source choices, things are a bit
different, but that doesn't mean it's always good to go hog wild
with any particular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/07 16:35, Mark Walker wrote:
LOL, I remember those days. Uh, can you hold on? My computer just
went down. or you need to fill out form 1203-B, send us $25 and we'll
get you the information you need in six weeks. Just kidding, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/07 13:20, Vivek Khera wrote:
On Jan 27, 2007, at 10:45 AM, Ron Johnson wrote:
Using slony or piped pg_dump requires that you have *double* the
amount of disk space. Having a *very large* database and double
capacity of SCSI disks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/07 16:05, tom wrote:
No.
Postgres does not represent an economic entity that can compete for $$
with Oracle.
It's also not nearly as popular. And I mean that in a very pop-culture
way.
How long did it take Oracle to support Linux?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 08:36, John Meyer wrote:
Joris Dobbelsteen wrote:
CREATE TABLE attendance
(
attendanceid serial primary key,
Why you have this??? You already have (entered,timeperiod,studentid)
that you can use, since that must be unique too. Try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 07:05, garry saddington wrote:
I have a table definition such as:
CREATE TABLE attendance
(
attendanceid serial primary key,
entered date DEFAULT current_date NOT NULL,
absent boolean,
authorization text default 'N',
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 10:43, A. Kretschmer wrote:
am Sun, dem 28.01.2007, um 10:25:33 -0600 mailte Ron Johnson folgendes:
Hi.
These fields do not use any disk space, as the data in them is
derived on the fly.
For example:
CREATE TABLE T_EXAMPLE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/07 15:18, garry saddington wrote:
On Sun, 2007-01-28 at 09:57 -0600, Ron Johnson wrote:
On 01/28/07 07:05, garry saddington wrote:
[snip]
When you say certain days, you mean days of the week?
If so, create a view like:
CREATE VIEW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/07 04:13, Anton Melser wrote:
On 26/01/07, Jim Nasby [EMAIL PROTECTED] wrote:
On Jan 25, 2007, at 12:47 PM, Benjamin Smith wrote:
On Tuesday 23 January 2007 13:55, Carlos wrote:
What would be the faster way to convert a 7.4.x database
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/07 11:50, Bill Moran wrote:
Bruce Momjian [EMAIL PROTECTED] wrote:
Devrim GUNDUZ wrote:
[snip]
Of course, the end of official support for a project doesn't prevent folks
with an interest from continuing to support it unofficially. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 13:37, Isaac Ben wrote:
On 1/26/07, Bruno Wolff III [EMAIL PROTECTED] wrote:
On Thu, Jan 25, 2007 at 10:47:50 -0700, Isaac Ben
[EMAIL PROTECTED] wrote:
[snip]
I plan on accessing the data with postgres via python and R. The
main
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 17:28, Shane Ambler wrote:
Bill Moran wrote:
I spend some time googling this and searching the Postgresql.org site,
but
I'm either not good enough with the search strings, or it's not to be
found.
I'm trying to plan upgrades so that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 20:12, Bruce Momjian wrote:
Ron Johnson wrote:
There is no set time frame planned that I know of.
It is more a matter of users that keep the old versions alive. Some with
large datasets on busy servers that can't allocate enough
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/07 21:48, Bruce Momjian wrote:
Ron Johnson wrote:
Yes:
http://www.postgresql.org/docs/8.2/static/migration.html
I was thinking of something like the release notes, but a bit more
targeted. (I know. diff the source.)
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/07 00:19, Martijn van Oosterhout wrote:
On Fri, Jan 26, 2007 at 10:16:39PM -0600, Ron Johnson wrote:
What are your plans for reducing the number of resources needed to
upgrade databases?
As noted, the table structure changes only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:30, Inoqulath wrote:
Hello Folks
Have a look at this Table:
CREATE TABLE foo(
id serial,
a_name text,
CONSTRAINT un_name UNIQUE (a_name));
Obviously, inserting a string twice results in an error (as one would
expect). But:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:34, Isaac Ben wrote:
Hi,
I'm trying to create a table with 20,000 columns of type int2, but I
keep getting the error message that the limit is 1600. According to
this message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:45, Thorsten Körner wrote:
Hi,
when I fire the following query:
select m_id, m_u_id, m_title, m_rating from tablename where m_id in (26250,
11042, 16279, 42197, 672089);
I will get the same results in the same order, as in in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 09:54, [EMAIL PROTECTED] wrote:
Ron Johnson wrote:
On 01/25/07 09:30, Inoqulath wrote:
[snip]
I think he is not asking How do I insert duplicate rows into a
unique-constrained column?, but rather that he wants to have the insert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/07 15:43, Bill Moran wrote:
In response to Mark Drago [EMAIL PROTECTED]:
[snip]
I don't think either of those are good ideas, because they both
rely on disk limits to trigger drastic changes in database size,
which will then require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/07 13:06, guillermo arias wrote:
Hello, i am Guillermo Arias, from Peru. I have a doubt about
capacity of tables. I am developing a software for accountants,
and my principal problem is about the table for the vouchers. I
have to decide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/07 17:22, Robert Sanford wrote:
It appears to me that there is some inconsistency in the date
calculations for my PostgreSQL install (version 8.0 on Win32).
January 07 of 2007 is a Sunday. Based on the documentation I would
expect that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 03:43, Alban Hertroys wrote:
Paul Lambert wrote:
G'day folks,
I'm faily new to the world of Postgre so excuse me if these
questions seem ignorant.
My current employer develops a software package which runs on
OpenVMS on HP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 07:09, Paul Lambert wrote:
Alban Hertroys wrote:
Paul Lambert wrote:
[snip]
I'd imagine there aren't too many VMS programmers around that
would be willing to port Postgres either, but if anyone out there
with experience in VMS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 08:22, Martijn van Oosterhout wrote:
On Mon, Jan 22, 2007 at 04:10:15PM +0200, Sim Zacks wrote:
How good is postgresql security?
Good, within limits.
For example, If I have data that I do not anyone to see, including the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 05:49, Peter Rosenthal wrote:
Right,
You also have to realize that your first query might return zero results,
and MySQL (and maybe this is correct SQL behavior) balks at an empty value
set where table_id in ().
I would expect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 09:55, Jan Muszynski wrote:
On 22 Jan 2007 at 16:10, Sim Zacks wrote:
How good is postgresql security? For example, If I have data
that I do not anyone to see, including the programmer/dba, is
it enough to change the password to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 14:01, Paul Lambert wrote:
Ron Johnson wrote: On 01/22/07 07:09, Paul Lambert wrote:
Alban Hertroys wrote:
Paul Lambert wrote:
[snip]
[snip]
We've got pretty new hardware - DS15's, DS25's, Itaniums and so
forth. But we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 16:55, Bruce Momjian wrote:
Engada wrote:
[snip]
When we got the PostgreSQL code from Berkely, it had code that
supposedly ran on VMS (not OpenVMS), but no one was available to
maintain it, so eventually it was removed.
DEC Marketing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/07 10:20, Joshua D. Drake wrote:
Shashank wrote:
[snip]
Where is this announcement? They don't need to drop either
engine, as both are GPL. MySQL as a group was never too hot
with BDB.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/07 18:21, Bruce Momjian wrote:
Sorry, I know of no way to get a status bar that shows how far the an
INSERT or COPY has progressed. People have asked for it, but no one has
any idea how to implement it.
How hard *would* it be to patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/07 10:52, Bruce Momjian wrote:
Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/07 18:21, Bruce Momjian wrote:
Sorry, I know of no way to get a status bar that shows how far the an
INSERT or COPY has progressed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/07 16:52, Michael Nolan wrote:
I have a MySQL table on our public website that is populated from a similar
table on our internal site, which runs PostgreSQL.
Recently I was trying to enhance one of our website queries and ran across
an
on my part, but it makes little difference in
either PostgreSQL or MySQL whether I use = or 'in'.
--
Mike Nolan
On 1/20/07, Ron Johnson [EMAIL PROTECTED] wrote:
Is this query created by an application? I.e, there might be a list
of PLR_EVENTIDs?
If so, I understand why it is like
-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 PostgreSQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/07 15:53, Jan Muszynski wrote:
Rather simple question, of which I'm not sure of the answer.
If I have a multiple column index, say:
Index index1 on tableA (foo,bar)
and I then:
Select * from tableA where foo = some value
values/combinations, so probably
it depends eh?
On Fri, 19 Jan 2007 16:57:42 -0600, Ron Johnson
[EMAIL PROTECTED] said:
On 01/19/07 15:53, Jan Muszynski wrote:
Rather simple question, of which I'm not sure of the answer.
If I have a multiple column index, say:
Index index1
-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 chars )
-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 output
-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
formats, right?
Right. In my case I have
-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 that even the
-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) that
-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 hoping that the query optimizer is smart
enough to see that if a query comes
-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
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 LA USA
Is common sense
-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.
Jefferson LA USA
Is common sense really valid?
For example, it is common sense to white-power racists
-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 to simultaneously dump data
.
- --
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 common sense is obviously wrong.
-BEGIN PGP SIGNATURE-
Version: GnuPG
.
Not really. You should read up on schemas and how they work. Plus the
addition of schemas and table spaces means you can infinite scaling
within the confines of your hardware itself.
infinite scaling within the confines of your hardware!
How is that accomplished?
- --
Ron Johnson, Jr
-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
tablenames.
Not really. You should
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 need to be in the multi-terrabyte
range.
I'm thinking more of RAM and CPU.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common sense
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.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common sense really valid?
For example, it is common sense to white-power racists that
whites
.
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 example, it is common sense to white-power racists that
whites are superior to blacks
-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 much higher than
, 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 to white-power racists that
whites are superior to blacks
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!
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common
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 Johnson, Jr.
Jefferson LA USA
(login_id) REFERENCES
n_logins(login_id) ON UPDATE CASCADE
n_traffic_traftype_id_fkey FOREIGN KEY (traftype_id) REFERENCES
n_traftypes(traftype_id) 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
, if for no other reason than
locality of data: the index will be smaller than the table, so
scanning it looking for record pointers should be faster than
scanning the table.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common sense really valid?
For example, it is common sense to white-power racists
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 blacks, and that those with brown skins
are mud people
...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 really valid?
For example, it is common sense to white-power racists that
whites are superior to blacks, and that those with brown skins
:
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
one gender or the other.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common sense really valid
next time.
- --
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 common sense is obviously wrong.
-BEGIN PGP SIGNATURE
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. As if they need instruction...
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common
... 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-power racists that
whites are superior to blacks, and that those with brown
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 brown skins
are mud people.
However, that common sense is obviously wrong.
-BEGIN
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 to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that common
, 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, it is common sense to white-power racists
-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,
I am wonderring if it is a good practice to use SERIAL index
* 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 common sense to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However
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 superior to blacks, and that those with brown skins
are mud people.
However, that common sense is obviously wrong
, but that's my 0.2
- --
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 common sense is obviously wrong.
-BEGIN PGP
/overlapping synthetic keys!
- --
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 common sense is obviously wrong.
-BEGIN PGP
, 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, Jr.
Jefferson LA USA
Is common sense really valid
a large IO impact on the main data volumes. I worry about how
long the 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
as primary. Many
things that will not change, ever, just were changed on the next meeting.
- --
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
?
I've seen this a lot, but I've always assumed that with the condition
that 'name' would NEVER change, there was no advantage.
- --
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
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 haul an artificial construct around.
On 11/24/06 12:38, Ben wrote:
It depends how it's going to be used
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 to white-power racists that
whites are superior to blacks, and that those with brown
-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 should include
of the software).
If you store the number in the database, I would suggest making the db
check the number on all input too. Otherwise you might end up with
invalid data in the database.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common sense really valid?
For example, it is common sense
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're going to
want to run your code on.
Or is he asking that this feature be added to PG?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common
(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 sense to white-power racists that
whites
-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:
On Nov 14, 2006, at 3:44 PM, Paul Silveira wrote
, 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 you with stripesets?
- --
Ron Johnson, Jr.
Jefferson LA USA
Is common sense
-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 a new directory, no?
You
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 superior to blacks, and that those with brown skins
are mud people.
However, that common sense is obviously wrong.
-BEGIN PGP SIGNATURE
, 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 superior to blacks, and that those with brown skins
.
Or you can concat several table-dumps to one big dump.
Note that the latter option does not guarantee that you get a consistent
dump.
What about 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
301 - 400 of 625 matches
Mail list logo
