This avoids the risk of creating any serious backwards-compatibility
issues: if there's anyone out there who does need SnapshotNow reads,
they just have to be sure to open the LO in read-write mode to have
fully backward compatible operation.
Comments, objections?
If you feel like it, feel free
On R, 2005-06-10 at 12:12 -0400, Tom Lane wrote:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > As the number of tuples between CTID_INDEX_MIN and CTID_INDEX_MAX is
> > finite, they must be added in finite time, by which time the index will
> > be up-to-date and usable for querie planner. (i.e. (1
On 2005-06-10, Kaare Rasmussen <[EMAIL PROTECTED]> wrote:
>> But not as easy as:
>> psql -c "reindex database {database}" {database}
>
> Well it was just to show that there really is no need for a program just for
> this functionality.
Either you're misunderstanding what "reindex database" does (
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 r
Yann,
> 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% threshold like the ext filesystem as an default for generating a
> war
> But not as easy as:
> psql -c "reindex database {database}" {database}
Well it was just to show that there really is no need for a program just for
this functionality.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unr
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Now that I think about it, maybe my problem is not related to TOAST at
> all, but to a corrupted varlena field.
Right.
> So if the corruption does not
> involve toasting, I'm in the same position as before, i.e. I haven't
> found out what is the corrup
Hi Tom,
On Fri, Jun 10, 2005 at 01:37:54PM -0400, Tom Lane wrote:
> Josh Berkus 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 back clean
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
> comprehen
Josh Berkus writes:
> I had a lot of time to kill on airplanes recently so I've gone
> digging through /contrib in an effort to sort out what's in
> there and try to apply some consistent rules to it.
Sorry for not responding sooner; I'm catching up on back email.
As already noted, I agree with
On Friday 10 June 2005 10:54 am, Kaare Rasmussen wrote:
> > actually I think part of the point of this was to give a command
> > line version of the reindex command, like we have for vaccum. If
> > that still matters, then it should probably stay. Actually it
> > should probably be converted to C
> actually I think part of the point of this was to give a command line
> version of the reindex command, like we have for vaccum. If that still
> matters, then it should probably stay. Actually it should probably be
> converted to C and moved to /src/bin.
>
Wouldn't something like
echo 'REINDE
Josh Berkus 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 back cleanly with a
> comprehensible error message rather than just having the datab
Bruce, Yann,
> Sure. Basically there has not been a lot of interest in this, and we
> are not sure how to implement it without a huge amount of work.
> Considering the other things we are working on, it hasn't been a
> priority, and lots of folks don't like the Oracle approach either.
Yeah. I'd
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Besides the MVCC issue, I am not sure it's a good idea LO being binded
> to OID. In my understanding OID is solely used to distinguish each LO
> in a database. In another word, it's just a key to LO. I think giving
> explicit key when creating a LO has som
This avoids the risk of creating any serious backwards-compatibility
issues: if there's anyone out there who does need SnapshotNow reads,
they just have to be sure to open the LO in read-write mode to have
fully backward compatible operation.
Comments, objections?
Besides the MVCC issue, I a
> I spent a little bit of time thinking about what it would mean exactly
> for large-object operations to obey MVCC, and decided that there are
> more worms in that can than I had realized. Part of the problem is
> that we have no concept of a lock on an individual LO, and thus
> operations that r
Teodor Sigaev <[EMAIL PROTECTED]> writes:
> Ok, I already realized WAL in GiST and tested with online backup. It works.
> Now I need test it on recovery after crash (power loss etc) and there is a
> problem in GiST with incompleted inserts, I hope, I resolved it, but this
> problem, I think, has
Yann Michel wrote:
> 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 possibilit
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
Ok, I already realized WAL in GiST and tested with online backup. It works.
Now I need test it on recovery after crash (power loss etc) and there is a
problem in GiST with incompleted inserts, I hope, I resolved it, but this
problem, I think, has the same nature as incompleted splits in btree co
Hannu Krosing <[EMAIL PROTECTED]> writes:
> As the number of tuples between CTID_INDEX_MIN and CTID_INDEX_MAX is
> finite, they must be added in finite time, by which time the index will
> be up-to-date and usable for querie planner. (i.e. (1) is done)
... and by which time, some more could have b
On Thu, 9 Jun 2005, Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Yeah it is an ordering problem with pg_dump...
If you are using pg_restore you can hack around the problem by using
pg_restore's load-order-control switch (which was invented exactly to
let people work around pg
I spent a little bit of time thinking about what it would mean exactly
for large-object operations to obey MVCC, and decided that there are
more worms in that can than I had realized. Part of the problem is
that we have no concept of a lock on an individual LO, and thus
operations that really shou
Yann Michel wrote:
> 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
On R, 2005-06-10 at 17:54 +0300, Hannu Krosing wrote:
> On R, 2005-06-10 at 09:47 -0400, Tom Lane wrote:
> > Hannu Krosing <[EMAIL PROTECTED]> writes:
> > > There are many ways this could be made to work, so it needs some
> > > discussion.
> >
> > (1) when do you ever catch up?
> >
> > (2) if your
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!
On R, 2005-06-10 at 09:47 -0400, Tom Lane wrote:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > There are many ways this could be made to work, so it needs some
> > discussion.
>
> (1) when do you ever catch up?
>
> (2) if your answer to (1) involves increasing the strength of a lock,
> how d
Dave Page wrote:
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> > Sent: 10 June 2005 15:31
> > To: PostgreSQL-development
> > Subject: [HACKERS] Tilde expansion on Win32
> >
> > I noticed that we don't expand tildes in
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> Sent: 10 June 2005 15:31
> To: PostgreSQL-development
> Subject: [HACKERS] Tilde expansion on Win32
>
> I noticed that we don't expand tildes in Win32 because of the use of
> tilde i
Bruce Momjian wrote:
I noticed that we don't expand tildes in Win32 because of the use of
tilde in short versions of long file names:
char *
expand_tilde(char **filename)
{
if (!filename || !(*filename))
return NULL;
/* MSD
On Fri, 10 Jun 2005 19:17:58 +0900
Junji TERAMOTO <[EMAIL PROTECTED]> wrote:
> Hello Mark,
>
> Mark Wong wrote:
> > http://developer.osdl.org/markw/postgrescvs/
>
> This site includes "Profile Report". It's very interesting and useful!
>
> Then, I compared result of 5/29 with the result of
I noticed that we don't expand tildes in Win32 because of the use of
tilde in short versions of long file names:
char *
expand_tilde(char **filename)
{
if (!filename || !(*filename))
return NULL;
/* MSDOS uses tilde for short
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
pg_terminate_backend()
exposing kill -SIGTERM to the client
The objections to this have not changed since last year; in fact they
are stronger because we have at least one report of actual trouble
with retail SIGTERMs.
I'm not
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
Yann Michel wrote:
> 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 ev
Hannu Krosing <[EMAIL PROTECTED]> writes:
> There are many ways this could be made to work, so it needs some
> discussion.
(1) when do you ever catch up?
(2) if your answer to (1) involves increasing the strength of a lock,
how do you avoid risk of deadlock?
regards,
Yann Michel wrote:
> 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.
No work has been done on it, and I don't even see a TODO item for it.
--
Bruce Momjian| http://candle.pha
Tom Flavel wrote:
> On 08/06/2005 21:57:29, Bruce Momjian wrote:
> > Andrew Dunstan wrote:
> > >
> > > surely somthing like
> > >
> > > foo_replace (source text, pattern text, replacement text, flags
text)
> > > returns text
> > >
> > > would fit the bill. OK, it reflects my Perl prejudices, but
Hello Mark,
(B
(BMark Wong wrote:
(B>http://developer.osdl.org/markw/postgrescvs/
(B
(BThis site includes "Profile Report". It's very interesting and useful!
(B
(BThen, I compared result of 5/29 with the result of 5/30.
(B
(B new-order transactions per minute
(B20050529 17
It seems that currently we do not allow modifying a table while an index
is built on it (at least my experience and some small tests I did
indicate it). Strangely I did not find a TODO item for it, so I may be
overlooking something and we already have it.
In case we really all
For big 24/7 tables
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
42 matches
Mail list logo
