Philip Warner <[EMAIL PROTECTED]> writes:
> At 12:31 AM 13/12/2002 -0500, Tom Lane wrote:
>> Amy does CREATE TABLE foo(f1 beths_type);
>> Beth now cannot drop her type beths_type.
>> In most circles this would be called a denial of service.
> Seems like a feature - if beth made the type public, sh
Janardhan <[EMAIL PROTECTED]> writes:
> Does it breaks any other things if all the index entries pointing the
> dead tuple are removed before reusing the dead tuple?.
Possibly you could make that work, but I think you'll find the
efficiency advantage you were chasing to be totally gone. The loc
At 12:31 AM 13/12/2002 -0500, Tom Lane wrote:
Amy does CREATE TABLE foo(f1 beths_type);
Beth now cannot drop her type beths_type.
In most circles this would be called a denial of service.
Seems like a feature - if beth made the type public, she has to deal with
fame. I don't see
Tom Lane wrote:
Janardhan <[EMAIL PROTECTED]> writes:
Does it breaks anythings by overwriting the dead tuples ?.
Yes. You cannot do that unless you've first removed index entries
pointing at the dead tuples --- and jumped through the same locking
hoops that lazy vacuum
On 13 Dec 2002 at 1:22, Bruce Momjian wrote:
> Replication
>
> I have talked to Darren Johnson and I believe 7.4 is the time to
> merge the Postgres-R source tree into our main CVS. Most of the
> replication code will be in its own directory, with only minor
> changes to o
On 12 Dec 2002 at 16:09, Stephan Szabo wrote:
>
> On Fri, 13 Dec 2002, [iso-8859-1] Diego T. wrote:
>
> > Hello I'm an Italian student of computer science at
> > University of Rome "La Sapienza". I've to analyze some
> > daemons which run under root privileges with a tool
> > developed by my dep
I wanted to outline some of the big items we are looking at for 7.4:
Win32 Port:
Katie Ward and Jan are working on contributing their Win32
port for 7.4. They plan to have a patch available by the end of
December.
Point-In-Time Recovery (PITR)
J. R. Nield did a
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> While playing around with a preliminary version of the information schema
> I get a failure in the type_sanity regression test here:
> SELECT p1.oid, p1.typname
> FROM pg_type as p1
> WHERE p1.typtype in ('b','d') AND p1.typname NOT LIKE '\\_%' AND NO
Patch applied. Thanks.
Backpatched to 7.3.
---
Teodor Sigaev wrote:
> This patch fixes minor bugs in dictionary generator in contrib/tsearch
> (contrib/tsearch/makedict/makedict.pl)
>
> Thank you.
>
> --
> Teodor Siga
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, so what do we do with 7.3.1. Increment major or minor?
>
> Major. I thought you did it already?
I did only minor, which I knew was safe. Do folks realize this will
require recompile of applications by 7.3 users moving to 7.3.1
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, so what do we do with 7.3.1. Increment major or minor?
Major. I thought you did it already?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive F
Philip Warner <[EMAIL PROTECTED]> writes:
> At 04:08 PM 12/12/2002 -0500, Tom Lane wrote:
>> Should we remove this error check, thereby effectively making
>> zero-column tables first-class citizens?
> The other option is to disallow the steps that resulted in the zero-column
> table in the first
OK, so what do we do with 7.3.1. Increment major or minor?
---
pgman wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Tom Lane wrote:
> > >> Wrong --- if you need a recompile then it's not binary
At 04:08 PM 12/12/2002 -0500, Tom Lane wrote:
Should we remove this error check, thereby effectively making
zero-column tables first-class citizens?
I should wait 2 minutes before hitting 'send'.
The other option is to disallow the steps that resulted in the zero-column
table in the first plac
At 04:08 PM 12/12/2002 -0500, Tom Lane wrote:
Should we remove this error check, thereby effectively making
zero-column tables first-class citizens?
It's a bit daft, but I suspect it's the way to go. There has to be a
non-zero chance that a future version of pg_dump may want to add attributes
Hello,
Using Postgresql 7.3 (CVS REL7_3_STABLE today), I received the following
error:
dropsites=> delete from cart_stores;
ERROR: heap_update: (am)invalid tid
This came from a database that was dumped from 7.2.1 using 7.2.1's pg_dump
and imported into 7.3. I was able to delete the rows indiv
On Fri, 13 Dec 2002, [iso-8859-1] Diego T. wrote:
> Hello I'm an Italian student of computer science at
> University of Rome "La Sapienza". I've to analyze some
> daemons which run under root privileges with a tool
> developed by my departement. This tool intercepts
> critical syscalls, like Exec
Hello I'm an Italian student of computer science at
University of Rome "La Sapienza". I've to analyze some
daemons which run under root privileges with a tool
developed by my departement. This tool intercepts
critical syscalls, like Execve, and blocks illegal
invocation of that primitives (E.g. Exe
While playing around with a preliminary version of the information schema
I get a failure in the type_sanity regression test here:
-- Look for basic types that don't have an array type.
-- NOTE: as of 7.3, this check finds SET, smgr, and unknown.
SELECT p1.oid, p1.typname
FROM pg_type as p1
WHERE
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Just for clarification --- don't most/all our releases make a binary
> change that needs are compile?
No, they usually don't. Adding new routines, for example, does not
break existing clients.
> What we do often is want old binaries to use our new
> li
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Wrong --- if you need a recompile then it's not binary-compatible, so
> >> it should be a major version bump.
>
> > But the previous poster said only API changes were reasons to bump the
> > major, right?
>
> Yes
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Wrong --- if you need a recompile then it's not binary-compatible, so
>> it should be a major version bump.
> But the previous poster said only API changes were reasons to bump the
> major, right?
Yes. He meant *binary* API changes,
Tom Lane kirjutas R, 13.12.2002 kell 02:08:
> I was bemused to notice that pg_dump is currently unable to dump the
> regression database. The domain regression test leaves an empty table
> (one with zero columns), which causes pg_dump to produce
>
> --
> -- TOC entry 172 (OID 675837)
> -- Name: d
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > So if a recompile fixes it, increment minor, else major.
>
> Wrong --- if you need a recompile then it's not binary-compatible, so
> it should be a major version bump.
But the previous poster said only API changes were reasons to bum
Bruce Momjian <[EMAIL PROTECTED]> writes:
> So if a recompile fixes it, increment minor, else major.
Wrong --- if you need a recompile then it's not binary-compatible, so
it should be a major version bump.
> Then we
> normally only do minor-level changes,. and frankly we improve the code
> all du
I was bemused to notice that pg_dump is currently unable to dump the
regression database. The domain regression test leaves an empty table
(one with zero columns), which causes pg_dump to produce
--
-- TOC entry 172 (OID 675837)
-- Name: domnotnull; Type: TABLE; Schema: public; Owner: postgres
--
Joe Conway <[EMAIL PROTECTED]> writes:
> I see we just recently made the word "value" reserved:
FYI, it's not reserved any more.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the un
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > We bump at the beginning only because we _know_ we want new users to use
> > the newer library. (Does the runtime linker know to get the highest
> > minor numbered library with the same major number?)
>
> No, the run-time linker only looks at
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.
---
Teodor Sigaev wrote:
> This patch fixes m
Bruce Momjian writes:
> We bump at the beginning only because we _know_ we want new users to use
> the newer library. (Does the runtime linker know to get the highest
> minor numbered library with the same major number?)
No, the run-time linker only looks at the major version.
> Bumping at the
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 12 December 2002 16:48
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Problem with function permissions
>
>
> "Dave Page" <[EMAIL PROTECTED]> writes:
> > I would not have expected public to now
"Dave Page" <[EMAIL PROTECTED]> writes:
> I would not have expected public to now have execute permission. Any
> reason for this, or is it a bug?
The default permissions for functions grant execute to public; the
system is just instantiating that default when you do an explicit grant.
The origina
I had the following behaviour reported by a pgAdmin user on PostgreSQL
7.3 (reproduced here on 7.3rc1 as it's all I have right now):
dave=# create function dave.testfunc() returns int4 as 'select 1 + 2'
language sql;
CREATE FUNCTION
dave=# select proacl from pg_proc where proname = 'testfunc';
p
Is there a way to get pg logging of plans to be produced in the terse
format like when a user types "explain select * from foo where bar = x"
The plan logging is very verbose. Having a lighter version of the
logging would be helpful in pinpointing troublesome queries without
slogging through pa
On Wed, 2002-12-11 at 19:00, Bruce Momjian wrote:
> It is an idea if no better one can be found, unless we don't want ALTER
> DOMAIN at all, which doesn't seem good.
I'll make a proposal for 'Object' locks as suggested, and we'll see
where we go from there.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP
This patch fixes minor bugs in dictionary generator in contrib/tsearch
(contrib/tsearch/makedict/makedict.pl)
Thank you.
--
Teodor Sigaev
[EMAIL PROTECTED]
tsearch_patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 4: Don't 'ki
Bruce Momjian wrote:
> If it is true that the linker only matches the major number, what value
> is there in incrementing the minor number, as we have done in the
> past?
It's main value is in indicating to the system administrator which
version of the library he has. This is particularly useful
37 matches
Mail list logo
