Hi,
first of all, thanks to all, that replied!
On Wed, Nov 16, 2005 at 08:28:31AM +0100, Martijn van Oosterhout wrote:
On Wed, Nov 16, 2005 at 08:09:31AM +0100, Yann Michel wrote:
Well, thanks for all the answers. Are the locks then released once they
are not needed any more like in 2PC
Hi Martijn,
On Wed, Nov 16, 2005 at 09:47:33AM +0100, Martijn van Oosterhout wrote:
Ah yes, PostgreSQL doesn't use 2PL, it uses MVCC. quick overview here:
http://linuxgazette.net/issue68/mitchell.html
THX! That was interesting!
Thanks. BTW: Is there anything about locks and their meaning
Hi,
On Wed, Nov 16, 2005 at 10:07:24AM -0500, Tom Lane wrote:
Yann Michel [EMAIL PROTECTED] writes:
Well, now that I'm thinking about, what you've written I think this is
exactly the point. I think, that there is a VACUUM waiting for the dump
to finish whereas the INSERTS are waiting
Hi all,
On Sun, Nov 13, 2005 at 03:22:23AM +0100, Yann Michel wrote:
I'm using PG_DUMP for backing up a postgres 7.4 database. As I have
seen, the pg_dump aquires a table lock while dump the table's content.
What will happen, if I have a basic table and several inherited tables
Hi,
On Wed, Nov 16, 2005 at 09:59:44AM +0800, Christopher Kings-Lynne wrote:
It acquires share locks on EVERY table.
do you mean on EVERY inherited table once one of them is dumped? Or do
you mean that a share lock is requested(and hold) on each of them once
one is dumped, i.e., sequentially?
Hi,
On Wed, Nov 16, 2005 at 01:25:43PM +0800, Christopher Kings-Lynne wrote:
I belive a lock is acquired on every table including inherited children
BEFORE doing ANY dumping. To allow pg_dump to get a consistent dump
snapshot.
Well, thanks for all the answers. Are the locks then released
Hi,
I'm just a little bit confused because I expected postgresql to be able
t connect by prior but as I have seen it is not. :-(
Are there any plans to support this in the main distribution? If have
found a patch to porstgres but I don't want to apply any patches but
only use the vanilla
Hi,
On Sat, Nov 12, 2005 at 03:27:32PM -0500, Jonah H. Harris wrote:
Yann,
I am working on the standard WITH syntax for recursive query support and
hope to get it into 8.2.
Fine! Looking forward to that!
Cheers,
Yann
---(end of broadcast)---
Hi,
I'm using PG_DUMP for backing up a postgres 7.4 database. As I have
seen, the pg_dump aquires a table lock while dump the table's content.
What will happen, if I have a basic table and several inherited tables.
Will the PG_DUMP tool only aquire locks on the inherited tables or on
the
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 for implmenting the maximum tablespace size
Hi folks!
On Tue, Jun 14, 2005 at 11:39:06AM -0600, Jonah H. Harris wrote:
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,
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 in the rain but
giving im a hint by time of what might happen if there was no action. I
have absolutely no
Hi Josh, hi jonah,
On Mon, Jun 13, 2005 at 12:36:12PM -0700, Josh Berkus wrote:
Don't get me wrong, I think we need tablespace maximums. What I'm
looking at is a user/group-based quota which would allow a superuser to
grant say, 2G of space to a user or group. Any object that user owned
Hi,
On Sat, Jun 11, 2005 at 09:45:12PM -0400, Gregory Maxwell wrote:
- Who has permissions to set the user's quota per tablespace, the
superuser and the tablespace owner?
It would be nice if this were nestable, that is, if the sysadmin could
carve out a tablespace for a user then the user
Hi Josh,
On Fri, Jun 10, 2005 at 02:25:11PM -0700, Josh Berkus wrote:
O.K. This makes sens to me. Otherwise I'd like to see quotas per
tablespace. As far as I got it, a tablespace may grow in size untile the
volume is full. Here a grace quota might be usefull as well. Let's say a
5%
Hi,
On Sat, Jun 11, 2005 at 05:36:34PM +0100, Dave Page wrote:
What do we need:
- Extension of the CREATE TABLESPACE command:
CREATE TABLESPACE tablespacename
[ OWNER username ]
[ SIZE integerK | M | G | T ]
LOCATION 'directory'
- Extension of
Hi,
did anything happen to implementing quotas, yet?
though I did not see anything on the TODO List I was wondering what is
going on.
Regards,
Yann
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Hi Bruce,
On Fri, Jun 10, 2005 at 09:45:32AM -0400, Bruce Momjian wrote:
did anything happen to implementing quotas, yet?
though I did not see anything on the TODO List I was wondering what is
going on.
No work has been done on it, and I don't even see a TODO item for it.
Do you think
On Fri, Jun 10, 2005 at 10:07:59AM -0400, Bruce Momjian wrote:
Do you think that it is possible that one can generate a TODO item out
of the request or do you rather think different?
Yes, sure. Ah, I found it. TODO has now:
* Allow limits on per-db/user connections
Fine!
That
Hi,
On Fri, Jun 10, 2005 at 10:59:46AM -0400, Bruce Momjian wrote:
Well, I have realy a lot of experiences with oracle usage and with its
limitation capabilities. What I need the most is space-limitation per
tablespace. Since 9i there is also a possibility to restrict cpu-usage
for a
Hi Josh!
On Fri, Jun 10, 2005 at 10:13:52AM -0700, Josh Berkus wrote:
Yeah. I'd prefer per-database quotas, rather than per-user quotas, which
seem kind of useless. The hard part is making any transaction which
would exceed the per-database quota roll back cleanly with a
Hi Tom,
On Fri, Jun 10, 2005 at 01:37:54PM -0400, Tom Lane wrote:
Josh Berkus josh@agliodbs.com writes:
Yeah. I'd prefer per-database quotas, rather than per-user quotas, which
seem kind of useless. The hard part is making any transaction which
would exceed the per-database quota roll
Hi Hannu,
On Thu, Jun 09, 2005 at 01:03:42AM +0300, Hannu Krosing wrote:
I was searching for some information about the storage of the user data
in postgresql. As far as I know there is one dictionary table for
storeing all the users of any known database, right?
As we'd like to
Hi,
I was searching for some information about the storage of the user data
in postgresql. As far as I know there is one dictionary table for
storeing all the users of any known database, right?
As we'd like to provide a postgresql database service to our students
we'd like to create one
Hi,
On Sun, Jan 23, 2005 at 12:16:31PM -0800, Josh Berkus wrote:
4) ignore backwards compatibility and just re-write the old views. I can
hear the shouting already ...
So, a choice of annoying options. Does anyone else on the channel have
opinions?
Isn't it a usefull option to
Hi,
as there were several questions about increasing performance in dwh
systems I was looking for some hints about how to pin an object to the
buffer so that they are not aged out due to the space is needed by any
other process or object. I know that in oracle you can do this by
defining a
Hi,
On Wed, Jan 19, 2005 at 11:54:50AM -0600, Bruno Wolff III wrote:
objects will use the default one. I think even count(*) queries could
benefit from this buffer-splitting due to indexes might be pinned to
this buffer pool.
This wouldn't have any special effect on count(*) queries.
Hi,
are there any plans for rewriting queries to preexisting materialized
views? I mean, rewrite a query (within the optimizer) to use a
materialized view instead of the originating table?
Regards,
Yann
---(end of broadcast)---
TIP 6: Have you
Hi,
On Wed, Dec 22, 2004 at 09:41:40AM +, Richard Huxton wrote:
UNION etc doesn't necessarily mean you can't update, so long as the
underlying table/key can be identified.
I think you mean UNION ALL, i.e. the set addition, don't you?
Otherwise UNION (wothout ALL) is kind of a aggregation
Hi,
On Fri, Nov 26, 2004 at 10:25:41AM -, Pawel Niewiadomski wrote:
My promoter accepted the subject. I'm waiting for an official acceptance
of the subject. Until then I would want to get familiar with PostgreSQL
internals and bitmap index implementations. I will appreciate
any links
Hi,
On Thu, Nov 04, 2004 at 11:26:41AM +0100, [EMAIL PROTECTED] wrote:
I would like to hear your opinion and whether anyone is interested in
helping.
I'd appreciate any kind of hints, helping me to understand the
modules/components and sources of each.
Regards,
Yann
Hi,
On Wed, Oct 27, 2004 at 10:13:56AM -0400, Greg Stark wrote:
There's a logical separation between the idea of index methods and table
storage mechanisms. Trying to implement something like this that breaks that
abstraction will only make things far more confusing.
I think what you're
Hi Tom,
On Fri, Oct 15, 2004 at 11:27:05AM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
On Thu, Oct 14, 2004 at 11:08:54PM +0200, Yann Michel wrote:
BTW: Is there any more documented CVS-version available? I mean it would
be really nice to read some comments from time
Hi,
On Sat, Oct 09, 2004 at 01:31:36PM -0400, Chris Browne wrote:
The most nearly comparable thing is be the notion of partial
indexes, where, supposing you had 60 region codes (e.g. - 50 US
states, 10 Canadian provinces), you might set up indices thus:
[...]
The partial indexes will
Hi,
On Thu, Oct 07, 2004 at 06:54:15PM -0400, Bruce Momjian wrote:
I'd like to know if there are any plans on introducing bitmap indexes
into postgresql. I think this could mean a big performance improvement
especially for datawarehousing applications. I know that there is an
index type
Hi,
On Fri, Oct 08, 2004 at 10:09:18AM +0100, Dave Page wrote:
I think what Reini was asking was why do you think you need bitmap
indexes as opposed to any existing type?
due to I'm developing a datawarehousing application we have lots of
fact-data in our central fact-table. As I know how to
Hi Josh,
On Fri, Oct 08, 2004 at 09:59:41AM -0700, Josh Berkus wrote:
Lots of people have talked about it but I don't know anyone coding it.
I would love to have bitmap indexes in Postgres, as would a lot of other
community members. However, they are far from trivial to code. Are you
Hi Josh,
On Fri, Oct 08, 2004 at 10:18:27AM -0700, Josh Berkus wrote:
I'd like to help you, but I think, that my C-Experience is not good
enough for beeing able to. I mean, I coded some C-stuff and I know how
bitmap indexes (should) work but I guess that this won't be enough. In
Hi,
I'd like to know if there are any plans on introducing bitmap indexes
into postgresql. I think this could mean a big performance improvement
especially for datawarehousing applications. I know that there is an
index type hash but I don't know how both types are comparable due to
they are both
Hi all,
I hope this is the right mailinglist for my question.
I'm using postgresql 7.2.1 and doing some bulk-loads from one table
to another. Due to sometimes there may exist som already loaded rows the
first thing I do is to delete them to reinsert all of them later on.
This sequence is but into
40 matches
Mail list logo
