? Are there any papers or researches about it?
Thank's a lot,
Pryscila.
-- Respectfully,Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporationhttp://www.enterprisedb.com/
)---
TIP 2: Don't 'kill -9' the postmaster-- Respectfully,Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation
http://www.enterprisedb.com/
)---TIP 6: explain analyze is your friend
-- Respectfully,Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporationhttp://www.enterprisedb.com/
ade the case that it would be useful to have, so go forth and
develop it. I don't see how there can be much more discussion
here.
On 9/8/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, Sep 08, 2005 at 12:02:54PM -0400, Jonah H. Harris wrote: I think what Greg suggested was sha1(num
huaxin... I'll save you the time... see the topic MUCH ADO ABOUT COUNT(*) and ADVANCED INDEX USAGE.
On 9/6/05, huaxin zhang [EMAIL PROTECTED] wrote:
not sure where to put this.I run two queries:1. select count(*) from table where indexed_column10;2. select * from table where indexed_column10;the
I agree with Josh on the UUID type, it gets abused far too often and
(IMHO) isn't widely enough used to belong in the core. Couldn't you just fix the problem in
pguuid rather than write a whole new type?On 9/6/05, Josh Berkus josh@agliodbs.com wrote:
Mark, I suggest that UUID be recommended in
The only time I've seen someone use UUIDs in PostgreSQL is when they
were converting from SQL Server. I've seen many bad data models
using UUID that could've/should've used normal sequences for
portability.
I look forward to seeing you're code.
Thanks!
On 9/6/05, nathan wagner [EMAIL PROTECTED]
Tom, you worded my thoughts much better than I did.
Bob, I too had heard that host-based UUIDs/GUIDs had issues with
uniqueness. I think Microsoft's implementation was hosed and they
ended up eliminating using the MAC completely.
I'll check out the code get back.
On 9/6/05, Bob Ippolito [EMAIL
Brook,
I have a lot of shell scripts that run as cron jobs and have considered
this option. However, if you look at it carefully, SQL is totally
different from say perl, php, bash, etc. for scripts which execute from
the shell. Tom is right, it is much more valuable and supportable to
call
of using a VM and bytecode?
Regarding Antlr etal, are there any that generate C code. I am more
familiar with the java parsers. If we can't generate C this is
probably a non-starter.
Dave
On 28-Jun-05, at 5:58 PM, Jonah H. Harris wrote:
Dave,
I lean with you and Tom. While running it over
Dave,
I lean with you and Tom. While running it over the same libpq protocol
would be helpful in some ways, it would have a lot of drawbacks and
would really change the function of libpq. I think a separate debugging
protocol is in order.
Also, as far as bytecode comments go, let's
I agree with Jan,
As part of my own projects I had to deal with the PL/pgSQL parser.
While it was a workable design at the beginning, it now makes some
things harder with the quoting etc.
Don't get me wrong, I've never really had any beef with PL/pgSQL, it has
worked great for a long time
Alvaro,
I agree, a protocol seems to generally be the best option.
-Jonah
Alvaro Herrera wrote:
On Thu, Jun 23, 2005 at 01:40:18PM -0400, Matthew T. O'Connor wrote:
Tom Lane wrote:
Denis Lussier [EMAIL PROTECTED] writes:
I got to thinking it'd be kewl if PgAdmin3
the
current patches?
-Jonah
Yann Michel wrote:
Hi again,
On Mon, Jun 13, 2005 at 04:47:20PM -0600, Jonah H. Harris wrote:
Well... a maximum tablespace size would be much easier to implement and
would still accomplish this level of quota for larger organizations and
database systems.
I vote
Tom,
You're right, this is going to take more work to make sure all is
perfect. Let me work up a formal definition and send it to the group.
Thanks for bringing me back to my senses.
-Jonah
Tom Lane wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
If I recall correctly, I never got
Sounds good to me... just wondering where dblink went? Is it going to
remain a part of the dist?
Sorry if this was already answered, I haven't had the time to check the
archive.
-Jonah
Tom Lane wrote:
Looking over the thread Josh started a few days ago, it seems there is
consensus to
As a near-daily PL/pgSQL developer, I similarly agree.
-Jonah
Andrew Dunstan wrote:
Pavel Stehule wrote:
What do you think about it? It's broke PL/SQL compatibility, I know,
but via last discussion I have opinion so Oracle compatibility isn't
main objective PL/pgSQL. There is some
So, are we going to go with 90% or 95% as the assumed assumption for a
warning :)
Yann Michel wrote:
I'd like to avoid a GUC for percent_full_warning if we can. Can anyone
see a way around this? Should we just assume 90% full?
Well, it was only an idea of not leaving the admin out
I prefer this option over a GUC.
Josh Berkus wrote:
People,
On second thought, we need to have a GUC for this, whether I want it or
not. It needs to be optional to the log, yes? So it would be:
log_tablespace_full = %
with the default being 0 (don't log).
On third thought, could
archives?
http://archives.postgresql.org
--
Jonah H. Harris, UNIX Administrator | phone: 505.224.4814
Albuquerque TVI | fax: 505.224.3014
525 Buena Vista SE | [EMAIL PROTECTED]
Albuquerque, New Mexico 87106| http://w3.tvi.edu/~jharris
issues with user-based quotas. But I'm
not the target audience so maybe I just don't understand.
--
Jonah H. Harris, UNIX Administrator | phone: 505.224.4814
Albuquerque TVI | fax: 505.224.3014
525 Buena Vista SE | [EMAIL PROTECTED]
Albuquerque, New
for different object kinds/types
i.e. one for indexes, one for dimensions and at least one for the fact
data in a dwh. So to allow users to store their comparable tables in the
appropriate tablespace you'd set up a quota for them.
Regards,
Yann
--
Jonah H. Harris, UNIX Administrator | phone
I wouldn't say it's enterprise-grade, but one could probably make it work.
Sean Davis wrote:
There is DBI-link, but this probably isn't an enterprise solution
http://www.pervasive-postgres.com/postgresql/tidbits.asp
Sean
On Jun 13, 2005, at 2:31 PM, Jonah H. Harris wrote:
The contrib
quotas in the catalog? I can go with an
aclitem-like array approach at the tablespace level or create a
pg_quota relation (aclitem-like array approach seems nicer, but you may
know something I don't)
Anything else you can think of, let me know.
Thanks.
--
Jonah H. Harris, Sr. Web Administrator
I have a patch for user quotas in (I think) 7.4.2. I was going to
update it for 8.x but have been too busy. The discussion (in the past)
was related to whether quotas would be applied to users or groups and
whether it would be on tablespaces (which I think it should).
I can spend some time
I would suggest adding it to \ds or create a \ds+ so that it is in
common with the rest of the commands.
-Jonah
Gevik babakhani wrote:
So what would be your suggestion in order to add this functionality?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Gevik,
You still didn't answer my question as to why you're reinventing the
wheel. Why not just work on updating techdocs instead?
-Jonah
Tom Flavel wrote:
On 04/06/2005 22:59:19, Gevik babakhani wrote:
Dear all,
The PostgreSQL Developer Network's Source Browser (beta1) is ready.
For this information, you can go through the code. I would suggest
reading through the catalog, heap access methods, storage manager, and
executor. Does anyone know of any good high-level docs on this?
Nithin Sontineni wrote:
Hi,
i want to know how create relation works and how
the
Is this really relevant to -hackers? I was thinking more along the lines
of -general.
Gevik babakhani wrote:
Dear All,
I am sure this is all asked before, so forgive me
Does anyone know (besides the documentation) if there is a graphical
representation of the pg catalog?
Regards,
Gevik.
Thanks!
Gevik babakhani wrote:
Regarding to update the techdocs and not reinveting the wheel, I am having a
mailng with Robert Treat of (webmaster pg) in order to see what can be
done.. any help is welcome... :)
Regards,
Gevik.
-Original Message-
From: Jonah H. Harris [mailto:[EMAIL
It's great that you want to help in this area, but wouldn't be a better
idea to revamp techdocs.postgresql.org?
Gevik babakhani wrote:
The idea behind the PGDN is to provide a knowledgebase for pg developers.
I was thinking about gathering howto's, articles, questions and answers and
Of
So, has anyone gone ahead and contacted Google yet?
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Cool. Thanks Marc.
Marc G. Fournier wrote:
Yes, been working on this since last night ...
On Thu, 2 Jun 2005, Jonah H. Harris wrote:
So, has anyone gone ahead and contacted Google yet?
---(end of broadcast)---
TIP 2: you can get off all
Marc,
If you wanted to submit PostgreSQL to Google for this, I'd be willing to
work with any potentials. Should someone choose to work on PostgreSQL
projects, the money can go to the group.
If anyone sees a problem with submitting under the PostgreSQL Global
Development Group, I can do it
official. We just need to tie up the loose ends on who
would be available to do the mentoring, which might need to be different
people depending on the work involved, unless you think you could handle all
comers Jonah?
Robert Treat
On Wednesday 01 June 2005 10:53, Jonah H. Harris wrote:
Marc
on 'mentor groups'? For instance, could
we create a 'mentors' mailing list, closed subscriptions, that
contained those willing to actively mentor, so that those being
mentor'd have multiple ppl's knowledge's to feed upon?
On Wed, 1 Jun 2005, Jonah H. Harris wrote:
My participation would
Thanks for adding this Bruce!
Is anyone going to be working on this immediately? If so, I'd be glad
to work with someone. Unfortunately, I don't have the time to devote to
taking something this big on, but I think it would be a really great
thing to have. Just let me know [EMAIL PROTECTED]
Hey everyone,
I'm sure this has been thought of but was wondering whether anyone had
discussed the allowance of run-time block size specifications at the
tablespace level? I know that a change such as this would substantially
impact buffer operations, transactions, access methods, the
Yes,
That is what I/my clients have been discussing. It is a nifty
performance feature.
Bricklen Anderson wrote:
Jonah H. Harris wrote:
Hey everyone,
I'm sure this has been thought of but was wondering whether anyone
had discussed the allowance of run-time block size specifications
any
information you'd like concerning this subject or any other I may
suggest. I don't want to waste your time, so if there is anything in
particular you want to see, just let me know. Thanks.
-Jonah
Tom Lane wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
I'm sure this has been
At a minimum I think we should support soundex in the core. I'm willing
to move soundex and metaphone into the backend. Does anyone see a
reason not to do so?
Douglas McNaught wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
Hey everyone,
I've been working with a couple people who
Peter,
I don't disagree with you that a more generalized function would also be
good, just that soundex is common and would be helpful if it were built-in.
Peter Eisentraut wrote:
Jonah H. Harris wrote:
At a minimum I think we should support soundex in the core. I'm
willing to move
Hey everyone,
I've been working with a couple people who didn't know that soundex and
metaphone were included in the distribution as contrib modules. While
it's their fault that they didn't check contrib, soundex is pretty
common among database systems and I was wondering if there was a
Kaare,
I have a utility which will read Ingres r3 data files directly but I
don't think it would be that reliable to use. I suggest you get one of
the open source database conversion utilities written in Java, they work
pretty well. You can find a few of them on SourceForge/Freshmeat.
I agree wholeheartedly and was actually just thinking of this yesterday.
Back when I was working on NEXTGRES I implemented package support into
plpgsql including scopes. While my time is pretty tight right now, I'd
be more than willing to work with whoever the plpgsql master is.
Jim C. Nasby
Hey everyone,
In addition to package support in plpgsql, it would be really handy to
have inline plpgsql. Likewise, I think there are others who feel this
way as-well.
Years ago, Oracle merged PL/SQL with their normal SQL parser which
allowed for inline PL/SQL. They did this because it was
David,
I agree with your idea. That seems like it would be somewhat easy to
implement and would do exactly what I would need. Anyone else have
ideas or thoughts along this line?
David Fetter wrote:
On Mon, May 09, 2005 at 11:44:23AM -0600, Jonah H. Harris wrote:
Hey everyone,
In addition
Did you not see the posts by Richard and Dennis?
ElayaRaja S wrote:
Hi,
I am unable to restart the PostgreSQL. I am using redhat Linux 9
with postgresql 7.4.5. Unexpectedly due to ups problem my server was
shutdown once. After that i am unable to restart the server. How to
stop and start.
Present
I'm familiar with the 2Q algorithm. I also remember seeing, I believe,
a public domain 2Q implementation floating around somewhere.
Tom Lane wrote:
I've been doing a bit of research on $subj, and coming to the conclusion
that the ARC patent is a lot narrower than it might appear. In fact
most
I'll dive into my bookmarks and see if I can find it.
Tom Lane wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
I'm familiar with the 2Q algorithm. I also remember seeing, I believe,
a public domain 2Q implementation floating around somewhere.
No doubt, but I think the more conservative
I found the reference I had seen. The engine was the Multicache
Simulation Environment written in C++. I can't find the code to it
anymore but I've contacted the author for a copy.
Jonah H. Harris wrote:
I'll dive into my bookmarks and see if I can find it.
Tom Lane wrote:
Jonah H. Harris
Simon,
You are correct. My negative experience with lock-free data structures
has been due to the different implementations I've tried. The theory
sounds good and no doubt, a good implementation could very likely be
developed with some time. I'm in no way against using lock-free data
Lock free data structures are cool... but not really applicable to
databases. They have a high maintenance overhead, severe complexity,
and will fail when there are many concurrent inserts/deletes to the
structure. I messed with them a year or so ago, and that's what I found
in every
Here's a possible solution... though I'm not sure about whether you find
the pg_ prefix appropriate for this context.
-- Create a Test Relation
CREATE TABLE test_tbl (
test_id BIGINT NOT NULL,
test_value VARCHAR(128) NOT NULL,
PRIMARY KEY (test_id));
-- Create COUNT
-0700, Jonah H. Harris wrote:
Lock free data structures are cool... but not really applicable to
databases. They have a high maintenance overhead, severe complexity,
and will fail when there are many concurrent inserts/deletes to the
structure.
Can you elaborate on when they would fail
We could still get their opinion.
I have a couple aquaintances at IBM that I can try to contact about it.
Rather than assume what IBM will do, why not just ask them? If they
don't respond, they don't respond. If they do respond, it's better than
us guessing.
Yes, it's only going to matter
D'Arcy J.M. Cain wrote:
I'm not sure why everyone wants to push this into the database anyway.
If I need to know the count of something, I am probably in a better
position to decide what and how than the database can ever do. For
example, I recently had to track balances for certificates in a
!
Respectfully,
Jonah H. Harris, Senior Web Administrator
Albuquerque TVI
505.224.4814
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
the speed, I'm offering to take it on and fix it.
Take this mesage as my willingness to propose and implement this
feature. Any details, pitfalls, or suggestions are appreciated.
Thanks again!
-Jonah
Tom Lane wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
Tom, Bruce, and others involved
Greg Stark wrote:
I think part of the problem is that there's a bunch of features related to
these types of queries and the lines between them blur.
You seem to be talking about putting visibility information inside indexes for
so index-only plans can be performed. But you're also talking about
Tom Lane wrote:
The fundamental problem is that you can't do it without adding at least
16 bytes, probably 20, to the size of an index tuple header. That would
double the physical size of an index on a simple column (eg an integer
or timestamp). The extra I/O costs and extra maintenance costs
Andrew Dunstan wrote:
Monetary cost is not the issue - cost in time is the issue.
cheers
andrew
We seem to be in agreement. I'm looking for faster/smarter access to
data, not the monetary cost of doing so. Isn't it faster/smarter to
satisfy a query with the index rather than sequentially
Rod Taylor wrote:
grow by about 40GB if this was done. Storage isn't that cheap when you
include the hot-backup master, various slaves, RAM for caching of this
additional index space, backup storage unit on the SAN, tape backups,
additional spindles required to maintain same performance due to
Jon Jensen wrote:
If you're willing to do the work, and have the motivation, probably
the best thing to do is just do it. Then you can use empirical
measurements of the effect on disk space, speed of various operations,
etc. to discuss the merits/demerits of your particular implementation.
Jeff Davis wrote:
Does someone know exactly what oracle actually does?
some old info resides here, http://www.orsweb.com/techniques/fastfull.html
I'll try and find something more recent.
---(end of broadcast)---
TIP 8: explain analyze is your
Bruno Wolff III wrote:
On Wed, Jan 12, 2005 at 14:09:07 -0700,
Jonah H. Harris [EMAIL PROTECTED] wrote:
Please keep stuff posted to the list so that other people can contribute
and learn from the discussion unless there is a particular reason to
limited who is involved in the discussion
Simon Riggs wrote:
Jonah,
People's objections are:
- this shouldn't be the system default, so would need to be implemented
as a non-default option on a b-tree index
- its a lot of code and if you want it, you gotta do it
Remember you'll need to
- agree all changes via the list and accept that
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
--
Jonah H. Harris, UNIX Administrator | phone: 505.224.4814
Albuquerque TVI | fax: 505.224.3014
525 Buena Vista SE
)---
TIP 7: don't forget to increase your free space map settings
--
Jonah H. Harris, UNIX Administrator | phone: 505.224.4814
Albuquerque TVI | fax: 505.224.3014
525 Buena Vista SE | [EMAIL PROTECTED]
Albuquerque, New Mexico 87106| http://w3
the group ownership be representative of
the user in question.
Rather ugly, and you'll run out of groups if you have alot of users (the
postgres user can only be in so many groups). It's a cute idea but I
really don't see it as being viable.
Stephen
--
Jonah H. Harris, UNIX Administrator | phone
to check?
Alvaro Herrera wrote:
On Thu, Jul 08, 2004 at 03:27:34PM -0600, Jonah H. Harris wrote:
Out of necessity, I've implemented user quotas in 7.4.3. What would the
process be for having this reviewed and combined? I have a patch for
7.4.3 ready, but wanted to know if you suggest that I patch
James Robinson wrote:
On Jul 9, 2004, at 12:04 PM, Jonah H. Harris wrote:
- Quota acts on any object owned by the user. Is this adequate for
everyone?
Does changing owner also trigger new quota calculations on both the new
and old owner?
Quota calculations are performed per-owner at commit
Stephen Frost wrote:
* Rod Taylor ([EMAIL PROTECTED]) wrote:
On Fri, 2004-07-09 at 11:47, Stephen Frost wrote:
* Klaus Naumann ([EMAIL PROTECTED]) wrote:
On Thu, 8 Jul 2004, Jonah H. Harris wrote:
3. The maximum quota size is (currently) the maximum of int4*1024 bytes.
why is this? This is very
requirement. Also, it would add a
great deal of complexity and computation time to calculate the soft
limit on every commit rather than requiring a vacuum analyze.
--
Jonah H. Harris, UNIX Administrator | phone: 505.224.4814
Albuquerque TVI | fax: 505.224.3014
525 Buena Vista SE
CHANGES ---
===
pg_shadow has added attribute userquota of type int4
pg_user view has added attribute (pg_shadow.userquota) to selection.
ADDED KEYWORDS
QUOTA
NOQUOTA
--
Jonah H
Neil,
I agree with Bruce and Tom. AFAIK and in my experience I don't think it
will be a significantly measurable increase. Not only that, but the
portability issue itself tends to make it less desireable. I recently
ported SAP DB and the coinciding DevTools over to OpenBSD and learned again
Is it just me, or is this not very clear?
Could you be more specific on what you need?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of fostered
Sent: Sunday, September 22, 2002 7:04 AM
To: [EMAIL PROTECTED]
Subject: [HACKERS] Will Pay for Help
I need
Are you using copy within a transaction?
I don't know how to explain the size difference tho. I have never seen an
overhead difference that large. What type of MySQL tables were you using
and what version?
Have you tried this with Oracle or similar commercial database?
-Original
Also, did you disable fsync?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jonah H. Harris
Sent: Friday, September 20, 2002 10:15 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [HACKERS] Improving speed of copy
Are you using copy within
Oracle 8.1.7.2
SQL SELECT to_char(0,'FM999.99') AS tst_char FROM dual;
TST_CHA
---
0.
SQL SELECT to_char(1,'FM999.99') AS tst_char FROM dual;
TST_CHA
---
1.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane
Sent: Wednesday, September
501 - 580 of 580 matches
Mail list logo
