Thanks for spotting this sloppy work. Basically, I cropped my diff because
there was lots of unrelated code in the work space. But I was a little too
hard and culled allfiles.sgml, alter.c, equal/copyfuncs.c and analyze.c.
I was wondering if something like that might have happened --- I know
you k
I have a whole separate CVS checkout for every path I'm working on -
makes life a lot easier :)
Dammit - I meant 'patch'.
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
I think this should be back ported for 8.0.2...
Chris
Bruce Momjian wrote:
Log Message:
---
Allow Win32 to support the O_SYNC open flag as an wal_sync_method method.
Magnus Hagander
Modified Files:
--
pgsql/src/include:
port.h (r1.69 -> r1.70)
(http://develo
I wonder how much back-compatibility and dump reloading problems this
might cause? :(
Tom Lane wrote:
Log Message:
---
Make the behavior of HAVING without GROUP BY conform to the SQL spec.
Formerly, if such a clause contained no aggregate functions we mistakenly
treated it as equivalent t
Completion of project to use fixed OIDs for all system catalogs and
indexes. Replace all heap_openr and index_openr calls by heap_open
and index_open. Remove runtime lookups of catalog OID numbers in
various places. Remove relcache's support for looking up system
catalogs by name. Bulky but mos
Is this a backport?
Bruce Momjian wrote:
Log Message:
---
Fix NUMERIC modulus to properly truncate division in computation.
Division rounding was causing incorrect results. Test case:
test=> SELECT 12345678901234567890 % 123;
?column?
--
> No, I don't think so. It doesn't seem to be something that enough
people use to risk the change in behavior --- it might break something
that was working. But, if folks want it backported we can do it. It is
only a change to properly do modulus for numeric.
Well, from my point of view it'
Don't forget the line in the GiST docs that says basically that WAL
logging is a SMOP:
http://developer.postgresql.org/docs/postgres/limitations.html
Chris
Tom Lane wrote:
Log Message:
---
Update text that stated GiST indexes aren't WAL-logged.
Modified Files:
--
pgsq
You could also mention under limitations that it's not NULL-safe perhaps.
Chris
Tom Lane wrote:
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
Don't forget the line in the GiST docs that says basically that WAL
logging is a SMOP:
http://developer.postgresql.o
-
- The current implementation of GiST within
- PostgreSQL has some major limitations:
- GiST index access is not concurrent, and the
- GiST interface doesn't allow the development of
certain
- data types, such as digital trees (see papers by Aoki et al).
-
AFAIK the GiST modifications s
BEGIN;
--
-- Name: SCHEMA public; Type: COMMENT; Schema: -; Owner: postgres
--
COMMENT ON SCHEMA public IS 'Standard public schema';
That's not what I would call guaranteeing that all the commands execute
successfully. What if the client encoding is unrecognized, for
instance?
How does this
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
How does this interact with the begin/commit placed around LOB dumps?
Good question ... right offhand it looks like there are some broken
things there (try grepping bin/pg_dump/ for BEGIN).
I suggest you just suppress the begin/comm
Good question ... right offhand it looks like there are some broken
things there (try grepping bin/pg_dump/ for BEGIN).
I suggest you just suppress the begin/commit for each LOB if
--single-transaction is specified, as it'd be in a single transaction
anyway...
Or...it could create and relea
Or...it could create and release a particular savepoint I suppose...I
don't know if there's much point in that though.
Didn't seem much point trying to remove it,
Huh? But it'll cause a total failure of dump restore?
Chris
---(end of broadcast)--
Perhaps you can explain further? My understanding was that the desired
functionality was that any failure would cause all aspects of the load
to fail also, so I don't see any problem with that; clearly I need to
listen to your thoughts.
Maybe we're not talking about the same thing? I was talkin
Chris, do you have a set-up to test out the blob behaviour? If your
using them in production you'll spot any further slip-ups; they weren't
intentionally ignored in the original patch.
No sorry - my PostgreSQL contribution these days primary consists of
"whining" :D
I usually just do this:
c
[EMAIL PROTECTED] (Teodor Sigaev) writes:
Log Message:
---
GIN: Generalized Inverted iNdex.
text[], int4[], Tsearch2 support for GIN.
So ... where's the documentation?
Will submit soon. Christopher Kings-Lynne kindly agreed to help us
with SGML and wording.
Just gimme some
Will submit soon. Christopher Kings-Lynne kindly agreed to help us
with SGML and wording.
Just gimme some time :)
Ok, I can look into this now...
I'm not sure really where to being though. What are all the new
operators? What does it even mean to use a GIN over an int[] column?
I
> Log message:
> Coerce unknown-literal-constant default values to the column type during
> CREATE TABLE (or ALTER TABLE SET DEFAULT), rather than postponing it to
> the time that the default is inserted into an INSERT command by the
> rewriter. This reverses an old decision that was intended to m
> Log message:
> Upgrade parsing code for ACLs to be less hokey and more cognizant of
> the actual logical structure and quoting rules being used. Fixes bug
> reported by Chris K-L on 7/8/03.
I vote for pg_get_acldef() class of functions...
Chirs
---(end of broadcast)--
Cool. That fixes the problem I was having perfectly.
Chris
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 03, 2003 3:04 AM
Subject: [COMMITTERS] pgsql-server/src/backend bootstrap/bootstrap.c ...
> CVSROOT: /cvsroot
> Modul
Did you deliberately misspell 'mistakes' below? Either way, it's very
amusing :P
Chris
On Sat, 20 Sep 2003, Tom Lane wrote:
> CVSROOT: /cvsroot
> Module name: pgsql-server
> Changes by: [EMAIL PROTECTED] 03/09/20 17:12:05
>
> Modified files:
> src/backend/catalog: sql_featur
Cool - I'm glad someone finally fixed that!
Chris
Tom Lane wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/09/25 20:02:12
Modified files:
src/backend/executor: execQual.c nodeFunctionscan.c
src/pl/plpgsql/src: gram.y pl_comp.c pl_exec.c
Log message:
Use pg_get_constraintdef() rather than pg_constraint.consrc; this is
a portion of a patch recently submitted by Christopher Kings-Lynne.
Applied by agreement that this is a bug fix.
You have actually technically done more than just fix the bug. Because
you
You have actually technically done more than just fix the bug. Because
you are passing in 'true' as the second parameter to
pg_get_constraintdef, you've enabled the 'pretty print' option... I'm
not sure it's that big a thing though...
Yeah, I know; that was deliberate. Any objections?
Not
I also notice that the 'Developer's FAQ' on the dev site that I think
Larry wrote might be a bit out of date. Talks about elog, and not
ereport, etc.
Chris
Bruce Momjian wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/29 16:20:12
Modi
Doh! I forgot all about that.
Chris
Tom Lane wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/30 23:58:16
Modified files:
src/tutorial : syscat.source
Log message:
Small fix to Christopher's recent improvements --- underscor
Do you have to commit these to the 7_4_STABLE branch as well?
Chris
Dave Cramer wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/11/03 11:28:26
Modified files:
src/interfaces/jdbc: build.xml
src/interfaces/jdbc/org/postgresql/jdbc2:
Are we going to be making the note in the release notes as we go from
now on?
Chris
Peter Eisentraut - PostgreSQL wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/11/06 18:08:15
Modified files:
doc/src/sgml : mvcc.sgml runtime.sgml
doc
Bit late isn't it? I thought the final release was now available?
Chris
Bruce Momjian wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/11/17 00:52:06
Modified files:
. : Tag: REL7_4_STABLE HISTORY
doc/src/sgml : Tag: REL7_
That's fixed it for me.
Chris
Tom Lane wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/12/08 12:39:05
Modified files:
src/bin/pg_dump: common.c pg_backup_archiver.h pg_backup_null.c
pg_backup_tar.c
Log message:
Log message:
Rename SortMem and VacuumMem to work_mem and maintenance_work_mem.
Make btree index creation and initial validation of foreign-key constraints
use maintenance_work_mem rather than work_mem as their memory limit.
Add some code to guc.c to allow these vari
Teach is_distinct_query to recognize that GROUP BY forces a subquery's
output to be distinct, if all the GROUP BY columns appear in the output.
Per suggestion from Dennis Haney.
Will this have should-be-in-release-notes side effects just as the
results of a DISTINCT over a
This should also definitely be in the release notes as a warning...
Chris
Neil Conway wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/03/04 17:47:18
Modified files:
doc/src/sgml : errcodes.sgml
src/backend/utils/adt: float.c oid.c
sr
Shouldn't we make this a totally new 'xml2' contrib, like we did for
tsearch2?
Especially since it is backwards incompatible and has a huge security
hole? (url fetching)
Chris
Bruce Momjian wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 0
* ALTER COLUMN TYPE. You can change a column's datatype to anything you
want, so long as you can specify how to convert the old value. Rewrites
the table. (Possible future improvement: optimize no-op conversions such
as varchar(N) to varchar(N+1).)
That seriously
Commit the reasonably uncontroversial parts of J.R. Nield's PITR patch, to
wit: Add a header record to each WAL segment file so that it can be reliably
identified. Avoid splitting WAL records across segment files (this is not
strictly necessary, but makes it simpler
Minor catalog cleanups for composite-type stuff. Adjust signatures shown
in pg_proc for record_in, record_out, etc to reflect that these routines
now make use of the second OID parameter. Remove the ancient SET entry
in pg_type, which is now highly unlikely to ever become used again.
Adjust type_
Hm? I think the recent discussion was about contracting not to
arbitrarily reassign OIDs for existing types. Nobody said anything
about not being able to remove types, especially not ones as dead as
this doornail was.
Yep, that's fine. I believe someone said that we'd never removed one
before,
Uh, why worry? If you had an application that depended in any way
shape or form on the SET type, then I already broke it ...
Wasn't it a pg_upgrade consideration or something?
Chris
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, p
Clean up generation of default names for constraints, indexes, and serial
sequences, as per recent discussion. All these names are now of the
form table_column_type, with digits added if needed to make them unique.
Default constraint names are chosen to be unique across their whole schema,
not jus
Fix oversight in recent ALTER TABLE improvements. We now support
ALTER TABLE tab ADD COLUMN col SERIAL, but we forgot to install the
dependency between the column and the sequence, so the sequence
would not go away if you dropped the table later.
What if you ALTER TABLE / TYPE SERIAL?
Chris
--
Cool, that fixes the detection for me.
Chris
Tom Lane wrote:
Log Message:
---
Check more test points (in fact, every week in 1970..2004) to get a more
accurate matching of our time zone to the system's zone. This method is
able to distinguish Antarctica/Casey from Australia/Perth, as in Ch
With \dp having a schema column, how would we display permissions there?
Access privileges for database "test"
Schema | Name | Type | Access privileges
+--+---+---
public | test | table |
(1 row)
I don't think it makes se
Is that the pg_dump half of the 'alter owner breaks non-default
privileges' bug fix?
Chris
Tom Lane wrote:
Log Message:
---
Fix incorrect tracking of session authorization in the presence of ACLs
that contain rights granted by non-owners. Per bug report from
Nishad Prakash.
Modified File
45 matches
Mail list logo
