On Thu, May 13, 2004 at 09:43:42AM -0400, Tom Lane wrote:
> BTW, what are your plans for state saving/reversion for the lock manager
> and buffer manager?
Ok, I have skimmed through the buffer manager code. At first I thought
I'd have to set something up in shared memory for this, but then I
not
Added to TODO:
* Allow GRANT/REVOKE permissions to be given to all schema
objects with one command
---
Tom Lane wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > Christopher Kings-Lynne <[EMAIL P
Milos Prudek wrote:
>
> > This is already fixed in CVS tip.
>
>
> Oh, cool!
>
> I know what is a CVS, but what is CVS tip?
>
> In which PostgreSQL stable release is upper() and lower() for Unicode
> planned to be included? Postgres version 7.5 ?
CVS tip is jus the current version of all CVS
Matthew T. O'Connor wrote:
> This weekend I am trying to fix up all known the pg_autovacuum issues
> that should be resolved for 7.4.3. I am aware of only two issues: temp
> table issues, and unchecked send_query() calls, if I am forgetting
> something, please let me know.
>
> 1) temp table issu
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Matthew T. O'Connor wrote:
> This weekend
I get this since Tom's commit.
On what platform? How is type time_t defined on your platform?
Hmmm, I just CVS up'd and all regression tests now pass...
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Sun, 23 May 2004, Tom Lane wrote:
> "Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> > There will always be people who won't read the notes, or ignore the
> > notes,
>
> Does anyone want to contemplate hacking things so that the Windows port
> reports a different version number? "0.1" might
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> First I initdb'd without TZ set. So every time I start the server I get
> LOG: could not recognize system timezone, defaulting to "Etc/GMT-4"
> HINT: You can specify the correct timezone in postgresql.conf.
I've fixed the minor issue here, which is t
On Sun, May 23, 2004 at 04:58:29PM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > First I initdb'd without TZ set. So every time I start the server I get
> > LOG: could not recognize system timezone, defaulting to "Etc/GMT-4"
> > HINT: You can specify the correct timezon
On Sat, May 15, 2004 at 02:08:39PM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Regarding the lock mechanism, I simply added some code to LockReleaseAll
> > so it gets the array of committed child Xids; on subtransaction abort,
> > the whole lock struct is scanned just li
I am back from camping and will be reading my email during the next few
hours.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> First I initdb'd without TZ set. So every time I start the server I get
> LOG: could not recognize system timezone, defaulting to "Etc/GMT-4"
> HINT: You can specify the correct timezone in postgresql.conf.
So what is your system timezone anyway (and
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> However, we still fail to sort small I (i dotless) and i. "i dotless"
> comes before i in Turkish Alphabet, but ORDER BY sorts i before "i
> dotless".
For that, you have to complain to your locale's designer. We just do
what strcoll tells us to.
I'm looking at the new timezone support.
First I initdb'd without TZ set. So every time I start the server I get
LOG: could not recognize system timezone, defaulting to "Etc/GMT-4"
HINT: You can specify the correct timezone in postgresql.conf.
Obviously the setup is wrong because DST doesn't
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
>> Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
>>> ... people want to be able to grant on all objects in a
>>> database, etc:
For things like this I use simple,
but super-powerful eval function:
CREATE OR REPLACE FUNCTION eval(text)
RETURNS
Hi,
On Sun, 23 May 2004, Tom Lane wrote:
> >> "pg_strncasecmp" that act like the above and replacing all calls of the
> >> standard library functions with these.
>
> > If you can post all the patches you'd like to apply, I'd be happy to test
> > them. (Sorry for the very late response, btw.)
>
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> On Thu, 6 May 2004, Tom Lane wrote:
>> What I'm thinking of doing is inventing "pg_strcasecmp" and
>> "pg_strncasecmp" that act like the above and replacing all calls of the
>> standard library functions with these.
> If you can post all the patches you'
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> There will always be people who won't read the notes, or ignore the
> notes,
Does anyone want to contemplate hacking things so that the Windows port
reports a different version number? "0.1" might give people the right
sort of impression about w
Hi,
On Thu, 6 May 2004, Tom Lane wrote:
> We're sort of halfway there on coping with the Turkish-locale i-vs-I
> problem. I'd like to finish the job for 7.5.
Cool!
> AFAICS the remaining problem is that there are a bunch of places that
> use strcasecmp() or strncasecmp() to match inputs agai
On Sat, 2004-05-22 at 23:44, Mark Kirkwood wrote:
> We could perhaps do something similar to the Apache 1.3 win platform
> notes, where they (still) say *something* like :
>
> "Apache on windows is not as stable as on unix... but is being actively
> improved all the time"
>
> This is a bit more
This is already fixed in CVS tip.
Oh, cool!
I know what is a CVS, but what is CVS tip?
In which PostgreSQL stable release is upper() and lower() for Unicode
planned to be included? Postgres version 7.5 ?
--
Milos Prudek
---(end of broadcast)---
TI
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
>> ... people want to be able to grant on all objects in a
>> database, etc:
> The right way to do this is to make sure there is a group that has access
> to "everything" and just add people to the
Milos Prudek <[EMAIL PROTECTED]> writes:
> PostgreSQL does not correctly use upper() and lower() for Unicode
> characters.
This is already fixed in CVS tip.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searche
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> 2) ALTER TABLE / DROP CLUSTER ON idx
> I like this form, however to make it work, we need to bump CLUSTER to
> being a reserved keyword.
I do not think this form is enough better than the other to justify
creating a nonstandard fully-reserved
On Sun, May 23, 2004 at 12:00:29 +0800,
Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> The latest thing we've noticed in the IRC channel and the phpPgAdmin
> lists is that people want to be able to grant on all objects in a
> database, etc:
The right way to do this is to ma
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> I get this since Tom's commit.
On what platform? How is type time_t defined on your platform?
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading throug
Neil Conway <[EMAIL PROTECTED]> writes:
> Does the following zero-column behavior strike anyone else as being a
> little strange? I can take a look at fixing this, I'm just curious if
> there's a consensus that the status quo isn't optimal.
I think that psql's table-pretty-printing logic gets sl
On 05/21/04:20/5, Tom Lane wrote:
> Hm. I do not think you can use an expression context callback for this
> anyway, because the callback won't be called in the case that query
> execution is abandoned due to an error.
> What you'd need for something like that is a global data structure that
> is
Here are the two syntaxes we can use for turning off clustering:
1) ALTER TABLE / SET WITHOUT CLUSTER
This will turn off clusting on any index on the table that has it
enabled. It won't recurse so as to match the CLUSTER ON syntax.
However, this form makes the non-standardy SET WITHOUT form more
Hi all,
Disclaimer: I'm not a C programmer and my knowledge of locales is
limited. I use Python.
PostgreSQL does not correctly use upper() and lower() for Unicode
characters. I've read the bug reports and followups at
archive.postgresql.org.
I'd like to propose two ideas:
1) Python has upper()
We could perhaps do something similar to the Apache 1.3 win platform
notes, where they (still) say *something* like :
"Apache on windows is not as stable as on unix... but is being actively
improved all the time"
This is a bit more positive than "it's dangerous!".
As for people not reading the
Hi guys,
The latest thing we've noticed in the IRC channel and the phpPgAdmin
lists is that people want to be able to grant on all objects in a
database, etc:
grant select on all tables to blah;
or even:
grant rule on all views in schema myschema to blah;
This seriously is asked every other day
It seems to me that we shouldn't copy them, but I'm having a hard time
putting a finger on why exactly. I guess it goes along with the fact
that we don't copy the database's owner, and any per-database variable
settings seem to me to be the database owner's decision to make.
Good points. The reas
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Anyone thought about this at all yet?
It seems to me that we shouldn't copy them, but I'm having a hard time
putting a finger on why exactly. I guess it goes along with the fact
that we don't copy the database's owner, and any per-database var
34 matches
Mail list logo
