I agree with most of this sentiment. Even knowing SQL and RDBMs reasonably
well, there is still a significant effort involved in moving from another
RDBMS (in my case Oracle) to postgres.
The postgres docs provide much all the detail (in a very concise form).
The hard part is putting all the diffe
Apologies, try this link instead:
http://miami.int.gu.edu.au/dbs/7016/a85397/state27a.htm#2067717
The previous one required you to be signed with technet - the one above
should be viewable by all.
John
John Sidney-Woollett said:
> I agree with most of this sentiment. Even knowing SQL and RDBMs
Hi all;
I am working on an outline for topics that I think should have detailed
discussion and/or tutorial items. Unfortunately my laptop is in the shop
(bad motherboard) but when it comes back, I will post it.
I think that Shrindhar is right-- these things do not belong in the main
documentatio
Alex Satrapa (Sunday 28 December 2003 22:16)
> Just convince your distribution's
My what? I don't use no stinkin' distribution :).
> postgresql package maintainer
That would be postgresql.org, I know not of binary packages.
> "suggests/recommends" portion of the package management metadata.
T
> I'm in a similar situation. My app is currently PG-only (although I
> _might_ be able to get it work with Firebird eventually). Currently I have
> to sell Linux to prospective clients in addition to my app. A native
> Windows version would make my life a bit easier.
Same here.
Our "clients" u
Andreas wrote:
Hello list,
what about uniqueness of inherited primary keys ?
eg you have :
create table objects (
id int4,
date_created timestamp(0),
primary key (id)
);
create table persons (
firstname varchar(100),
lastname varchar(100)
) inherits (objects);
now ...
insert into object
A documentation system like the one over at http://php.net, would be
fantastic for Postgresql. There could be lookups based on SQL commands,
Functions, and Sitewide Searches. This alone would go a long way to
expose PHP to "the masses".
In terms of using MySQL or Postgresql, lets all face it, m
Seastian Böck wrote:
for primary keys there is a simple (and at least working for me)
solution as long as you can use the SERIAL type for your primary
key.
[...]
Now the id column gets merged and you should have the desired
behaviour.
If you want objects.id to get referenced by other tables you ha
Hi!
I need have records on different languages simultaneously on some DB
for i18n of my application. Application is multilingual.
I decide use for this UNICODE. (UNICODE is encoding for my cluster)
But PostgreSQL do not work properly with UNICODE :(
I have the following problems:
1) ORDER BY is n
This has been an interesting thread, with lots of well
considered contributions. The consensus seems to be
"PostgreSQL is plenty good enough and more, we just
need more people to know it, and an easier learning
path".
What bothers me a little here is an apparent lack of
awareness of the work of t
To all,
The facts:
PostgreSQL 7.4.0 running on BSD 5.1 on Dell 2650 with 4GB RAM, 5 SCSI
drives in hardware RAID 0 configuration. Database size with indexes is
currently 122GB. DB size before we completed the vacuum full was 150GB.
We have recently done a major update to a table, f_pageviews
Chris Travers (Sunday 28 December 2003 20:56)
> Also, here in Indonesia, most of these B&B's charge less than $30/night.
> Purchasing a new system (often $700 or more) is the equivalent of 23
> room-nights (for a place which typically has fewer than 10 rooms). Used
> PC's are out of the question b
Tony <[EMAIL PROTECTED]> writes:
> ... I DO believe however that a decent introduction to
> the more important concepts (Triggers, Fkeys, Stored Proc, Views) that
> people from lesser systems (MySQL, Access) may not be familiar with.
> What they do, how they help, and why they are generally a go
To all,
The facts:
PostgreSQL 7.4.0 running on BSD 5.1 on Dell 2650 with 4GB RAM, 5 SCSI
drives in hardware RAID 0 configuration. Database size with indexes is
currently 122GB. Schema for the table in question is at the end of this
email. The DB has been vacuumed full and analyzed. Between
Jeff,
I agree; we have an apparent lack of awareness of many things. IMO this
is more indicative of a lack of a unified presence than anything else.
part of the project is on gborg, part of the project is on advocacy,
etc.
How would a newbie know to go look for advocacy.postgresql.org ?.
Da
Is your system using full RAM? Ie, what does limits -a show?
Regards.
Fernando.
En un mensaje anterior, Sean Shanny escribió:
> To all,
>
> The facts:
>
> PostgreSQL 7.4.0 running on BSD 5.1 on Dell 2650 with 4GB RAM, 5 SCSI
> drives in hardware RAID 0 configuration. Database size with inde
Take a look at datasize: your processes are allowed a maximum of 512 Mb RAM.
Read the handbook to find out how to reconfigure your kernel and the limits
(and/or ulimit) man page to tweak the values for individual processes.
Good luck!
Fernando.
En un mensaje anterior, Sean Shanny escribió:
> lim
Sean Shanny <[EMAIL PROTECTED]> writes:
> Does anyone have an explanation as to why this might occur?
What have you got vacuum_mem set to? Also, what ulimit settings is the
postmaster running under? (I'm wondering exactly how large the backend
process has grown when it gets the failure.)
Sean Shanny <[EMAIL PROTECTED]> writes:
> update f_commerce_impressions set servlet_key = 60 where servlet_key in
> (68,69,70,71,87,90,94,91,98,105,106);
> ERROR: out of memory
How many rows will this try to update? Do you have any triggers or
foreign keys in this table? I'm wondering if the l
Fernando Schapachnik <[EMAIL PROTECTED]> writes:
> Take a look at datasize: your processes are allowed a maximum of 512 Mb RAM.
> Read the handbook to find out how to reconfigure your kernel and the limits
> (and/or ulimit) man page to tweak the values for individual processes.
512Mb does not seem
From postgresql.conf:
# - Memory -
shared_buffers = 1 # min 16, at least max_connections*2,
8KB each
sort_mem = 64000# min 64, size in KB
vacuum_mem = 32767 # min 1024, size in KB
The ulimit is set to unlimited as far as I can tell.
--sean
Tom Lane wr
Hi,
My problem is rather complex. I will try to explain it clearly (I hope !)
Sorry for my poor english.
I'm tracking change of state for entities (something than can be
monitored.)
The set of states are limited (state1 to state5.)
A table is storing the current state for each entities, and an
Tom,
There are no FK's or triggers on this or any of the tables in our
warehouse schema. Also I should have mentioned that this update will
produce 0 rows as these values do not exist in this table. We have a
dimension table named d_servlet that holds servlet names and id's.
This table is
(BOn Dec 27, 2003, at 8:06 PM, Joe Conway wrote:
(B
(B> Mike Mascari wrote:
(B>> but not 07-Temporal. Is that right? From a cursory search on temporal
(B>> support, it appears that there should be a 07-SQL/Temporal group.
(B>
(B> Your correct -- I didn't realize that it was its own spec. A
Andreas wrote:
Seastian Böck wrote:
for primary keys there is a simple (and at least working for me)
solution as long as you can use the SERIAL type for your primary
key.
[...]
Now the id column gets merged and you should have the desired
behaviour.
If you want objects.id to get referenced by othe
D. Dante Lorenso wrote:
You can do this by adding a trigger to your table. Just define the
trigger
to be invoked on INSERT and UPDATE for your table. The trigger
definition
would look something like this: [...]
Thanks.
So far that works for one table.
Can I have this behaviour somehow inherit
Sean Shanny <[EMAIL PROTECTED]> writes:
> sort_mem = 64000# min 64, size in KB
You might want to lower that; a complex query could easily use several
times sort_mem. Whether this is the immediate source of your problem
with the other query is hard to tell.
> vacuum_mem = 32767
Sean Shanny <[EMAIL PROTECTED]> writes:
> There are no FK's or triggers on this or any of the tables in our
> warehouse schema. Also I should have mentioned that this update will
> produce 0 rows as these values do not exist in this table.
Hm, that makes no sense at all ...
> Here is output fr
Tom,
I will lower the sort_mem and see what happens. :-)
I agree that we probably pushed the limits of a vacuum full with the
size table we had and the large percentage of change in the table. We
did NOT run any vacuum jobs during the update process, that my have
helped to allow the updates t
Tom,
As you can see I had to reduce the number of arguments in the IN clause
to even get the explain.
explain update f_commerce_impressions set servlet_key = 60 where
servlet_key in (68,69,70,71,87,90,94);
Hello,
How about just a "Getting Started with PostgreSQL" guide... Python is
like this.
They have the "real" documentation but they also have a introductory
tutorial. We
could have a brief document (100 pages or less) that talks about the
basic concepts
of PostgreSQL...
Sincerely,
Joshua D.
Quoting Shridhar Daithankar <[EMAIL PROTECTED]>:
> On Monday 29 December 2003 12:47, Tom Lane wrote:
> > Shridhar Daithankar <[EMAIL PROTECTED]> writes:
> > > That is right. but that fact remains that postgresql documentation is
> > > just sufficient. If you read the manual and follow it religousl
> name | state | from_date | to_date
>
> foo | state2 | |
> foo | state1 | |
> bar | state4 | |
> ...
> foo | state3 | |
I would consider using only 1 table, where a NULL to_date indicates the
current state, and you have a compound inde
Quoting "Joshua D. Drake" <[EMAIL PROTECTED]>:
>
> >This concerns me. This is the second time recently someone has said
> something
> >is NOT documented and it it turn out it is.
> >
> >So my question is (no offense to anyone) are the web sites not "clear"
> enough to
> >find information quickly
The documentation needs to be opened up and interlinked a lot more. For
instance, one of the things that makes the PHP site work well, is
linking to related functions at the end of each function's description, eg:
http://us2.php.net/manual/en/function.pg-fetch-all.php
However, check our PG docum
How would this differ from the existing Tutorial?
Well, for one it would tell the user how to start postgresql ;)
Yes I know that it provides a link to chapter 14 but IMHO the
tutorial should be inclusive. New users don't want to
jump all over a 1000 page document to figure out how to
just sta
On Mon, Dec 29, 2003 at 14:31:43 -0500,
"Keith C. Perry" <[EMAIL PROTECTED]> wrote:
>
> Shridhar,
>
> I tend to agree with you. I personally think the docs are very good and have
> the techical depth warranted for a product like PostgreSQL. On the other hand
> for the ad & m (advocacy and mar
"Grant Allen" <[EMAIL PROTECTED]> writes:
> Basically, I want to turn off backslash ( \ ) as an escape character
> in string literals.
No can do without hacking backend code. But why are you more concerned
about backslash than, say, single-quote (')? I cannot envision any way
of embedding arbitr
Tom,
We can give you access to the machine Tom. We need to know what sort of
access you require. Since I don't have the ability to correspond with
you via email due to the earthlink filter you have on could you send me
another email address privately or a phone number or smoke signal so we
c
On Sun, 28 Dec 2003, Keith C. Perry wrote:
> > Admittedly this deterrent won't stop a determined newbie from finding
> > what they are after, but I'm sure there are some folk who would just
> > assume that postgres is deficient in this area. Note some previous posts
> > from others which demonstra
"Ericson Smith" <[EMAIL PROTECTED]> Wrote:
> A documentation system like the one over at http://php.net, would be
> fantastic for Postgresql. There could be lookups based on SQL commands,
> Functions, and Sitewide Searches. This alone would go a long way to
> expose PHP to "the masses".
>
Here is
On Mon, 29 Dec 2003, Jeff Eckermann wrote:
>
> Isn't this what books are supposed to be for? i.e. to
> fill in the gaps or provide the coverage, tips, howtos
> etc. etc. that no-one really expects formal
> documentation to cover. There are quite a few good
> books out there, including two access
On Mon, 29 Dec 2003, Martin Marques wrote:
>
> I haven't read the latest review of Bruce's book, but I can recall that the
> original version started with:
>
> In this chapter, you will learn how to connect to the database server and
> issue simple commands to the POSTGRESQL server.
>
> At t
Tom,
The big difference ... all DBs (at least, the ones I listed, including PostgreSQL)
support the single quote as it's own escape character - so no difference when it comes
to app porting (yes, PostgreSQL has the \' method as well, but '' works across the
board).
The big P's atypical handing
On Sat, 27 Dec 2003, Chris Travers wrote:
> Date: Sat, 27 Dec 2003 18:44:48 +0700
> From: Chris Travers <[EMAIL PROTECTED]>
> To: Marc G. Fournier <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
> [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Is my MySQL Gaining ?
>
>
> In s
45 matches
Mail list logo
