On Tue, 11 Jul 2006, Ken Johanson wrote:
Does anyone know roughly when there might be an 8.2 beta? Would a rough guess
of about November be right (1 year after 8.1)?
that woudl be a safe ball park ... we're currently in the process of
working up to feature freeze for August 1st ...
Hi All,
I have a database where I give priviledges solely by user membership in
permitted roles (groups).
It works flowlessly, but when I tried to assign CREATEUSER priviledge to
an administrator ROLE (just one database administrator, not the
postmaster), I have to explicitly SET ROLE ADMIN
On Tue, 2006-07-11 at 15:24 -0500, Ron Johnson wrote:
Joshua D. Drake wrote:
It is also something that users are clammoring for (and my customers). To
the point that I have customers using unions to emulate the behavior. Why?
Because it is really, really fast.
When inserting multiple
On Tue, 2006-07-11 at 21:11, Alvaro Herrera wrote:
Maybe we could check the MCVs, and store those for which the plan would
be A (say indexscan) and those for which it would be B (say bitmap
indexscan), etc; so we'd save more than one plan and choose at execution
time depending on the actual
2006/7/11, Oisin Glynn [EMAIL PROTECTED]:
Paul Tilles wrote:
Version postgres 7.4.7:
Following sql
UPDATE tablename SET value = 0.0 where value!=-9.4;
results in the error message
ERROR: operator does not exist: smallint !=- integer
HINT: No operator matches the given name and
We have PostgreSQL 8.1 running on Windows 2000 for a few
weeks now, when we try to start the service, it could not
start claiming no error returned. So, I go to the command
prompt and run the following:
C:\Program Files\PostgreSQL\8.1\bin\pg_ctl.exe runservice
-N pgsql-8.1 -D
Thanks for the tips. I will try to use the strict pragma as you suggested
and see if it helps.
The code runs fine most of the time. The issue is as time elapses, the
server ends up crashing. Generally, it will crash within a day of use
(with only 3 clients hitting it). The reason we
I apologize for not including the server information in the last e-mail. I
knew I would forget something. :)
PostgreSQL 8.1.4 (compiled from source)
Debian GNU/Linux 3.1
Intel(R) Pentium(R) D CPU 3.00GHz
1GB RAM
We have not be able to test the triggers anywhere else that has any load on
it.
On 7/11/06, Alvaro Herrera [EMAIL PROTECTED] wrote:
Guido Neitzer wrote:
On 11.07.2006, at 19:36 Uhr, Merlin Moncure wrote:
It is not, as prepared statements have the problem that they are only
optimized once and very generically and without actual knowledge of
the parameter content, this is
On Jul 12, 2006, at 4:24 AM, zordax wrote:
What tool are you using to create users/passwords? If you are
using a GUI tool, have you tried to replicate the problem using psql?
After a while i think it might be a problem of tool. Because i can
login by psql. But i have this effect with
I w'd like how the DB growth impacts the actual disk
space. For example, I have a table with one textfield,
char(20) and I insert 100 records. My DB size w'd
be approximately,
20+28(Overhead)=48*100=48MB. What is the actual
effect on the physical HDD. I w'd appreciate your
help.
Thanks,
Hello,
I'm using Crystal
Reports 8.5 against PostgreSQL Database Server 8.1.
The thing is that
when I try to use an SQL _expression_ Field in Crystal, doesn't work (it does work
when I don't use it).
Returns the
following error:
Error in compiling
SQL _expression_:
Cannot find parser
I w'd like to know how the DB growth impacts the actual disk
space. For example, I have a table with one textfield,
char(20) and I insert 100 records. My DB size w'd
be approximately,
20+28(Overhead)=48*100=48MB. What is the actual
effect on the physical HDD. I w'd appreciate your
help.
Bruno Wolff III wrote:
On Tue, Jul 11, 2006 at 06:05:18 -0700,
[EMAIL PROTECTED] wrote:
Hello,
I'm a pgsql novice and here is what I'm trying to do:
1.I need to create a dynamic table with the column names fetched
from the database using a select statement from some other table.
On Tue, Jul 11, 2006 at 04:26:41PM -0400, Paul Tilles wrote:
Yes. That works. I think that the parser should work properly either way.
You're mistaken. PostgreSQL by design makes it possible for you to
define a custom operator like !=- and use it.
Paul
Bruce Momjian wrote:
Paul Tilles
Is there a way to get the names of the arguments to a function from
psql? /df and /df+ return the parameter types, but not their names.
Thanks,
Tim
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
You should use varchar(20), which will not consume as much space as
char(20) IF the values inserted don't, themselves take the full 20
positions. In varchar, there will be no padding, thus saving on your disk
space.
For your question in particular, that depends on the block size of how PG
On 07/12/2006 09:25:45 AM, Jan Wieck wrote:
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored
if i understand well you need to have an history for your products.i would have a table B withdate products price1/1/2006 prod1 1.01/1/2006 prod2 3.0or replace prod_name py product_id, ... Thomas On Jul 12, 2006, at 16:08, [EMAIL
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Anyway, 20
On Fri, 2006-07-07 at 22:41 +, [EMAIL PROTECTED] wrote:
[mailto:[EMAIL PROTECTED] On Behalf Of Adrian Klaver
I guess the solution depends on what is a 'large amount of data'. The
most time consuming part is going to be converting the single data
elements at the top of each sheet
On 7/12/06 3:32 AM, Rafal Pietrak [EMAIL PROTECTED] wrote:
On Tue, 2006-07-11 at 15:24 -0500, Ron Johnson wrote:
Joshua D. Drake wrote:
It is also something that users are clammoring for (and my customers). To
the point that I have customers using unions to emulate the behavior. Why?
I think that that's the answer, put the whole OS and db on a
bootable cd or DVD. In 20 years they'll surely be no
problem running the whole thing from RAM so media access
speed should not be an issue.
You are correct. I thought that CD only had a shelf life of 5 to 10 years.
This is true
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl O. Pinc wrote:
On 07/12/2006 09:25:45 AM, Jan Wieck wrote:
On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
On Mon, 2006-10-07 at 10:33 -0700, Karen Hill wrote:
Hello,
How would one go about creating a US telephone type in the format of
(555)-555- ? I am at a loss on how it could be accomplished in
the most correct way possible while not going into the various
different country styles e.g.
# [EMAIL PROTECTED] / 2006-07-11 12:04:07 -0400:
On 6/30/2006 1:07 PM, Merlin Moncure wrote:
* mysql has a few features here and there which are nice...just to
name a few, flush tables with lock, multiple insert, etc
(...)
The multiple insert stuff is not only non-standard, it also
On 7/12/2006 12:18 PM, Tim Hart wrote:
Wouldn't you run into driver problems if you tried to restore a 20 year old
image? After all, you probably won't be using the same hardware in 20
years...
I can't even find the same hardware I bought last year. That's one of
the reasons why I use VMware
Hello, pgsql-general!
I originally posted this to pgsql-sql, but after not seing any
response for roughly a day and after re-reading the charters, I felt
that pgsql-general might be more appropriate.
What I've got here are a couple of ON INSERT rules for a view. The
second rule is what I'm
On Wednesday 12 July 2006 08:37, Richard Broersma Jr wrote:
I think that that's the answer, put the whole OS and db on a
bootable cd or DVD. In 20 years they'll surely be no
problem running the whole thing from RAM so media access
speed should not be an issue.
You are correct. I
On Wed, Jul 12, 2006 at 07:33:09AM -0700, Timothy Perrigo wrote:
Is there a way to get the names of the arguments to a function from
psql? /df and /df+ return the parameter types, but not their names.
One way would be to look at pg_proc.proargnames.
Wouldn't you run into driver problems if you tried to restore a 20 year old
image? After all, you probably won't be using the same hardware in 20
years...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jan Wieck
Sent: Wednesday, July 12, 2006 9:26 AM
To:
Jan Wieck [EMAIL PROTECTED] writes:
I can't even find the same hardware I bought last year. That's one of the
reasons why I use VMware on my laptop. It has a hardware abstraction layer
that
presents default XVGA and Soundblaster cards etc. to the guest OS. When I buy
a
new laptop, I just
On Wed, 2006-07-12 at 07:32, Carl M. Nasal II wrote:
I apologize for not including the server information in the last e-mail. I
knew I would forget something. :)
PostgreSQL 8.1.4 (compiled from source)
Debian GNU/Linux 3.1
Intel(R) Pentium(R) D CPU 3.00GHz
1GB RAM
We have not be able
On Wed, 2006-07-12 at 05:55, Clodoaldo Pinto wrote:
2006/7/11, Oisin Glynn [EMAIL PROTECTED]:
Paul Tilles wrote:
Version postgres 7.4.7:
Following sql
UPDATE tablename SET value = 0.0 where value!=-9.4;
results in the error message
ERROR: operator does not exist:
On 7/12/06, Timothy Perrigo [EMAIL PROTECTED] wrote:
Is there a way to get the names of the arguments to a function from
psql? /df and /df+ return the parameter types, but not their names.
select oid::regprocedure from pg_proc where proname like 'your name here';
merlin
On Wed, Jul 12, 2006 at 07:08:15 -0700,
[EMAIL PROTECTED] wrote:
Thank you for the suggestions.
I will try to describe the problem better.
I have two problems to solve. First one is that I have to transpose a
table.
I have table A that looks like this:
date product price
-- Forwarded message --
From: Marco Bizzarri [EMAIL PROTECTED]
Date: Jul 12, 2006 9:03 PM
Subject: Re: [GENERAL] Long term database archival
To: Karl O. Pinc [EMAIL PROTECTED]
Long term archival of electronic data is a BIG problem in the
archivist community. I remember, a few
On Wed, Jul 12, 2006 at 07:55:49 -0300,
Clodoaldo Pinto [EMAIL PROTECTED] wrote:
I have already counted 6 very similar answers. Is there some problem
with the list software that prevents people from noticing it has
already been answered?
In my case, my mail server had been heavily loaded
Marc,
Mailing lists are showing an ungodly slowness. To the tune of 2 hours for
things to show up. What's up?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive
On Wednesday 12. July 2006 21:03, Marco Bizzarri wrote:
Long term archival of electronic data is a BIG problem in the
archivist community. I remember, a few years ago, a paper describing
the problem of historical (20+ years old) data which were running the
risk of being lost simply because of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Hart wrote:
Wouldn't you run into driver problems if you tried to restore a
20 year old image? After all, you probably won't be using the
same hardware in 20 years...
Scarily, the current PC architecture is just a set of add-ons and
NM I found the documentation.
Joseph Shraibman wrote:
Joshua D. Drake wrote:
Secondly this sounds like a perfect time for you to consider upgrading
to 8.1
and making use of table partitioning.
How does that work, exactly?
---(end of
Joshua D. Drake wrote:
Secondly this sounds like a perfect time for you to consider upgrading to 8.1
and making use of table partitioning.
How does that work, exactly?
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Scott Marlowe wrote:
On Wed, 2006-07-12 at 05:55, Clodoaldo Pinto wrote:
2006/7/11, Oisin Glynn [EMAIL PROTECTED]:
Paul Tilles wrote:
Version postgres 7.4.7:
Following sql
UPDATE tablename SET value = 0.0 where value!=-9.4;
results in the error message
ERROR: operator does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leif B. Kristensen wrote:
On Wednesday 12. July 2006 21:03, Marco Bizzarri wrote:
Long term archival of electronic data is a BIG problem in the
archivist community. I remember, a few years ago, a paper
describing the problem of historical (20+
I'm trying to assist the XRMS developers port their application to
postgres (8.1.x on), and it's almost there. One (perhaps the only) stumbling
block is case for table and column (relation and attribute) names.
Apparently MySQL allows for mixed case, while postgres wants only lower
case. One of
On Wednesday 12 July 2006 17:33, Rich Shepard wrote:
I'm trying to assist the XRMS developers port their application to
postgres (8.1.x on), and it's almost there. One (perhaps the only)
stumbling block is case for table and column (relation and attribute)
names. Apparently MySQL allows for
On Wed, 12 Jul 2006, Rich Shepard wrote:
I'm trying to assist the XRMS developers port their application to
postgres (8.1.x on), and it's almost there. One (perhaps the only) stumbling
block is case for table and column (relation and attribute) names.
Apparently MySQL allows for mixed
On Wed, 12 Jul 2006, Joshua D. Drake wrote:
Likley, not ever ;)...
Hi, Josh!
That's fine with me. As long as postgres works, I'm happy.
ERROR: relation role_id already exists
AHA! I see what is happening... you can't have an index name the same as a
table name. Tell them just to change
On Wed, 12 Jul 2006, Stephan Szabo wrote:
AFAIK, SQL says that an non-quoted identifier such as Foo is treated as
FOO (case-folded to upper). PostgreSQL currently treats it as foo
(case-folded to lower). Quoted identifiers are not case-folded and are
compared case-sensitive.
So, for example
Looking into it ... server is quiet, and from the headers, the
anti-virus/spam stuff is causing neglible delay ... last time this
happened, it turned out to be a bad subscribe address in the list, so will
be searchign through that next ...
On Wed, 12 Jul 2006, Joshua D. Drake wrote:
Marc,
Rich Shepard [EMAIL PROTECTED] writes:
I'm trying to assist the XRMS developers port their application to
postgres (8.1.x on), and it's almost there. One (perhaps the only) stumbling
block is case for table and column (relation and attribute) names.
Apparently MySQL allows for mixed case,
On Wed, 12 Jul 2006, Tom Lane wrote:
It's probably worth pointing out here that the MySQL behavior they seem to
be expecting is considerably further from the spec than Postgres's
behavior. If I'm reading between the lines correctly, they are expecting
foo and Foo (both written without
Merlin Moncure [EMAIL PROTECTED] writes:
On 7/12/06, Timothy Perrigo [EMAIL PROTECTED] wrote:
Is there a way to get the names of the arguments to a function from
psql? /df and /df+ return the parameter types, but not their names.
select oid::regprocedure from pg_proc where proname like 'your
Just today i have noticed i have one certain table that i cannot delete
any records from
1 have delete all Triggers, Vacuumed the tables removed all foreign keys
that linked to this table.
--
*Jamie Deppeler
*Database Administrator
*once:technologies pty ltd
*
*Do It Once!*
46 Roseneath
Last I tried, a few years ago, Crystal 8.5 would not work at all with
PostgreSQL. Version 9 works but the later service packs handle it much
better.
Can you browse the table data through the database expert?
Mike
On Wed, 2006-07-12 at 10:23 -0300, Juan Ignacio Lalla wrote:
Hello,
I'm
On Thu, Jul 13, 2006 at 01:45:36PM +1000, Jamie Deppeler wrote:
Just today i have noticed i have one certain table that i cannot delete
any records from
What happens when you try to delete? Do you get an error? Does
the delete succeed but report zero rows deleted? Something else?
What does
57 matches
Mail list logo
