I'm thinking about attacking pg_dump's lack of knowledge about using
dependencies to determine a safe dump order. But if there's someone
out there actively working on the problem, I don't want to tread on
your toes ... anyone?
I've done a whole lot of _thinking_, but basically no _doing_, so go
r
Yeah, I think the main issue in all this is that for real production
sites, upgrading Postgres across major releases is *painful*. We have
to find a solution to that before it makes sense to speed up the
major-release cycle.
Well, I think one of the simplest is to do a topological sort of objects
Why should ALTER COLUMN change the column number, i.e. position?
Because it creates a NEW column.
It may be that programmers should not rely on this, but it happens,
and in very
large projects. If we can avoid unexpected side-affects like moving the
columns position, then I think we should.
T
Marcel Kornacker did implement concurrency for GiST - I confirmed as
much with Joe Hellerstein (his advisor). I know there's a paper he
wrote with C.Mohan on it. I don't know which version his
implementation was for.
The 7.4 GiST docs have a link to Kornacker's thesis that details how to
implement
PostgreSQL most definitely works great on Solaris x86 !
At UC Berkeley, we have our undergraduate students hack on the
internals of PostgreSQL in the upper-division "Introduction to
Database Systems" class ..
http://www-inst.eecs.berkeley.edu/~cs186/
Hi Sailesh,
You know what would be kind of coo
HOWEVER, a release cycle of *less than 6 months* would kill the advocacy vols
if we wanted the same level of publicity.
I do support the idea of "dev" releases. For example, if there was a "dev"
release of PG+ARC as soon as Jan is done with it, I have one client would
would be willing to test
Will adding the logical attribute number break all of the external
tools? pg_dump, etc are all dependent on attnum now?
Would it be possible to keep the meaning of attnum the same externally
and add another column internally to represent the physical number?
Interesting idea. It would require a
Oh, and yeah, a win32 port. Yay, another OS port. Postgres runs on dozens of
OSes already. What's so exciting about one more? Even if it is a
pathologically hard OS to port to. Just because it was hard doesn't mean it's
useful.
I don't call porting Postgres to run well on something like 40% of the
eg. Someone who just knows how to use postgres could test my upcoming
COMMENT ON patch. (It's best if I myself do not test it) Someone with
more skill with a debugger can be asked to test unique hash indexes by
playing with concurrency, etc.
I forgot to mention that people who just have large,
That said, I'm not really sure how we can make better use of the beta
period. One obvious improvement would be making the beta announcements
more visible: the obscurity of the beta process on www.postgresql.org
for 7.4 was pretty ridiculous. Does anyone else have a suggestion on
what we can do to p
BTW, one main consideration is that all the postgres admin apps will now
need to support ORDER BY attlognum for 7.5+.
But that is only really important if they've also used the ALTER TABLE
RESHUFFLE COLUMNS feature. So if they make one alteration for 7.5, they
need to do another. That seems fai
Right now, I believe we are looking at an April 1st beta, and a May 1st
related ... those are, as always, *tentative* dates that will become more
fine-tuned as those dates become nearer ...
April 1st, or 4 mos from last release, tends to be what we aim for with
all releases ... as everyone knows, w
Wait for confirmation from at least one other developer perhaps, buy you
can try this:
1. Set attisdropped to false for the attribute
2. Set the atttypid back to whatever the oid of the type of that column
is/was (Compare to an undropped similar column)
3. Use ALTER TABLE/SET NOT NULL on the
Everyone on -hackers should have been aware of it, as its always
discussed at the end of the previous release cycle ... and I don't think
we've hit a release cycle yet that has actually stayed in the 4 month
period :( Someone is always 'just sitting on something that is almost
done' at the end th
The time from release 7.3 to release 7.4 was 355 days, an all-time high.
We really need to shorten that. We already have a number of significant
improvements in 7.5 now, and several good ones coming up in the next few
weeks. We cannot let people wait 1 year for that. I suggest that we aim
for a
Right -- AFAICS, the only change in COPY compatibility would be if you
COPY TO'd a table and then changed the logical column order in some
fashion, you would no longer be able to restore the dump (unless you
specified a column list for the COPY FROM -- which, btw, pg_dump
does). I don't think it wi
-- value-independent transition function
CREATE AGGREGATE newcnt (
sfunc = int4inc, basetype = 'any', stype = int4,
initcond = '0'
);
COMMENT ON AGGREGATE newcnt (any) IS 'an any agg comment';
ERROR: syntax error at or near "any" at character 30
COMMENT ON AGGREGATE newcnt (any) IS NULL;
ERR
I made up a more thorough regression test for date input formats, and
found that there were still some cases that were rejected :-(. Attached
is a more complete patch that handles all month-name cases, and
explicitly can not change the behavior when there's not a textual month
name. Documentation
I propose the attached patch to fix the problem. It doesn't break any
regression tests, and it appears to fix the cases noted in its comment.
Opinions on whether to apply this to 7.4?
I think it should be fixed, since it could cause applications to break.
Shouldn't you also add a regression test
Check that you don't need to use the -p option at all.
Also, make sure you remove any ^M (DOS CR) characters from the line
endings. That always happens to me if I receive the emailon a windows
machine and save the attachment, windows sometimes likes to rewrite all
the line endings, causing the
I anyone going to email the people who last reported the unsupported
platforms to see if they'll re-test?
Shall I? Or should someone more official?
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Hey Bruce,
When you get around to it, can you commit the patch I submitted that
dumps conversions in pg_dump. I need that in to complete my COMMENT ON
patch.
I think it's pretty safe to apply, and I'm not 100% sure I still have a
local copy of the patch, so I can't let it drift too much :(
C
Jan checked in the ARC changes last night, and he and Tom ran into
some problems, leading to that being pulled back out, while he
revisits the code.
It's back in again, and appears to work now (at least the regression
tests pass ... no idea about performance ...)
I actually managed to hang my pro
Even if they weren't useful for anything else, I think there's value in the
developers having to consider what is optional and what is not. This need
for constant review probably reduces the chance of bloat, over time even
in the full tarball.
How about dropping the partial tarballs and using the s
Is the problem with backing up and restoring a database which has tsearch2
installed and enabled delt with in Version 7.4 of PostgreSQL?
If it's the problem with restoring the tsearch2-related functions, then no,
and I'm not sure whether it's "fixable" (in the sense that a tsearch2 enabled
datab
I thought the whole problem here is that OIDs are unsigned ints, hence
intVal() won't allow the highest OIDs?
Exactly. That's why you need to handle T_Float too. See the int8
example, which has just the same problem.
It occurs to me then that I could just then use FloatOnly in the grammar
and
| COMMENT ON LARGE OBJECT NumericOnly IS comment_text
n->objname = makeList1(makeAConst($5));
Forget the makeAConst step --- it's just wasted cycles. In the
execution routine, you can use code comparable to define.c's defGetInt64()
to convert the Value node into a numeric OID, ie, either do in
The only idea I have is to call oidin() to do the conversion from string
to oid. I see this in copy.c:
loaded_oid = DatumGetObjectId(DirectFunctionCall1(oidin,
CStringGetDatum(string)));
if (loaded_oid == Inval
Seriously, I have wondered if it might be a good idea to assemble a
small "hit team" that would take some high profile open source projects
and make sure they worked with Postgres. Bugzilla would be the most
obvious candidate, but there are certainly others. I suspect that could
be quite produc
The "doesn't quite make the best use of PG" quote is one of the best
examples of buck-passing I've seen in awhile. If Bugzilla had been
designed with some thought to DB independence to start with, we'd not
be having this discussion.
You have to laugh at an app that actually uses MySQL's replicati
People occasionally seem to ask for keeping time stamps on schema objects
(tables, functions, etc.) about when they were created and last altered
(in their structure, not the data in the tables). I think that this would
be a relatively useful and painless feature. What do others think?
It has act
Hey - now that we have a branch, is Bruce going to start committed the
pgpatches2 list?
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTE
Just wondering how often the stats collector resets it self. Is this a
parameter i can change?
At my knowledge each time that you do an analyze on
your db your statistics are changed ( are not incremental
I mean), anyway you can set to reset statistics at the
start of postgres.
I think you're mix
I think we had agreed that formerly-listed contributors would not be
deleted, but would be moved to a new section titled "Contributors
Emeritus" or some such. Please make sure that Tom Lockhart and Vadim
get listed that way, at least.
I think the "Emeritus" word might be too hard for non-native En
* Fix uselessly executable files in the source tree. See my recent post.
Any ideas on that?
As far as I'm aware, the only way to fix this is to get into the cvsroot
and chmod them by hand.
Chris
---(end of broadcast)---
TIP 5: Have you checked
This is my first patch for PostgreSQL against the 7.5devel cvs (please advise if this is the wrong place to post patches). This patch simply enables the \xDD (or \XDD) hexadecimal import in the copy command (im starting with the simple stuff first). I did notice that there may be a need to issue
I keep getting this:
pg_regress: initdb failed
Examine ./log/initdb.log for the reason.
rm regress.o
gmake[2]: Leaving directory `/home/chriskl/pgsql/src/test/regress'
gmake[1]: Leaving directory `/home/chriskl/pgsql/src/test'
-bash-2.05b$ more src/test/regress/log/initdb.log
Running in noclean mo
D'oh, just clued into the 'java' aspect ... Joshua, will this run as a
JSP, remotely, through Jakarta-Tomcat? One of the limitations of pgAdmin,
as far as I'm concerned, is the fact that you can run it remotely
Then use phpPgAdmin...
Chris
---(end of broadcast)---
Has anyone looked at this yet?
http://developer.postgresql.org/docs/postgres/unsupported-features-sql99.html
Have we implemented a bunch of those Array features now?
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choo
Numerics are a LOT slower than reals. Integers are faster than anything
I guess.
Chris
Mark Wong wrote:
I don't remember making a conscious decision between the number and integer
database type. Is that a significant oversight on my part?
On Fri, Oct 31, 2003 at 08:04:34PM -0500, Rod Taylor w
In any case, can't 7.3 pg_dump use the 7.4 libpq?
If not then the major version should be bumped.
My point being that I would like to actually preserve my cluster
settings and stuff when dumping...
So it's pg_dump, not libpq, that's important to me.
Chris
---(end of bro
Hey guys,
Is there any way we could build a static version of the 7.4 pg_dump, to
make it easy to dump existing databases using the 7.4 dump? Otherwise,
it's quite difficult to arrange to have two different postgres
installations, etc...
Chris
---(end of broadcast)-
See attached regression.diffs.
Chris
parallel group (5 tests): select_views portals_p2 cluster foreign_key rules
select_views ... ok
portals_p2 ... ok
rules... FAILED
foreign_key ... ok
cluster ... ok
parallel group
Does anyone have anything ready to put into CVS as soon as we start v7.5,
or shortly afterwards?
Check bruce's 7.5 patches list (can't remember the address though :) )
I have this COMMENT ON thing ready to go, except for this darn taking in
unsigned ints from the parser business that I haven't h
FreeBSD 4.9 was released today. In the release notes was:
2.2.6 File Systems
A new DIRECTIO kernel option enables support for read operations that
bypass the buffer cache and put data directly into a userland buffer.
This feature requires that the O_DIRECT flag is set on the file
descriptor a
AFAICT there was no discussion about this issue when the patch was
proposed and applied. But now that the point is raised I have to say
that I don't like this change. I don't think system catalogs should be
excluded from tab completion. They never were before 7.4, and I have
not seen anyone com
OK, doesn't look like we are going to add the ability to turn off
constraint checking for reload, nor add ANALYZE as part of ALTER TABLE
ADD FOREIGN KEY, so we only have a few items left.
Hey - what about if you just delete the pg_constraint entries for all
your foreign keys, then won't they all b
Only regproc adds the unnecessary pg_catalog. qualification, why is that?
Er, I couldn't see the part of your example where that happened?
Basically, my question is why ::regproc alone always addes the catalogue
qualification in this case?
Rows below correspond to:
::regtype
::regtype
::regpro
I thought you said that yesterday?
Chris
Bruce Momjian wrote:
Time zone changes --- will be OK tomorrow.
---
Christopher Kings-Lynne wrote:
I'm still seeing Horology failures on FreeBSD 4.9...
See attached diff.
When you do this query:
SET SEARCH_PATH TO pg_catalog;
SELECT castsource::pg_catalog.regtype AS castsource,
casttarget::pg_catalog.regtype AS casttarget,
castfunc::pg_catalog.regprocedure AS castfunc,
castfunc::pg_catalog.regproc AS castfunc2 FROM pg_catalog.pg_cast ORDER
BY 1, 2;
Only regpr
I'm still seeing Horology failures on FreeBSD 4.9...
See attached diff.
Chris
*** ./expected/horology.out Thu Sep 25 14:58:06 2003
--- ./results/horology.out Tue Oct 28 11:29:24 2003
***
*** 577,583
SELECT (timestamp with time zone 'today' = (timestamp with time zone
However, you're not the first to get burnt by this mis-assumption,
so maybe we should do something about it.
The low-tech solution to this would be to stop listing the default
values as commented-out entries, but just make them ordinary uncommented
entries. That way people who think "undoing my ed
I think because START TRANSACTION is SQL standard? However, I thought
BEGIN WORK was SQL standard, and we don't support READ ONLY there
either --- hmmm.
BEGIN is no part of the SQL standard. The only way to begin a
transaction under the SQL standard is START TRANSACTION.
Chris
-
Hi guys,
Is there _any_ way of sorting by a regproc as it appears, not as its
underlying OID?
Chris
---(end of broadcast)---
TIP 8: explain analyze is your friend
Hi guys,
I've asked this of a few people now, but I haven't managed to get a
straightforward solution.
I'm working on COMMENT ON LARGE OBJECT.
If you could help me with this one, it would be really cool. Other than
this, comment on language, conversion, cast and operator class are all done.
Th
This would imply that every little read would have to do a scan on a table
to find the row and then to perform the substr. An open command can
be optimized a lot more, for example to cache entries that have been
opened so that it's fast to read the next 1kb or whatever you want.
It's an index sc
OK, do we want to put back the mention of these in the release notes?
The non-zulu ones sound pretty strange to me and might be better left
undocumented.
What's there to go in the release notes? We haven't changed any code,
and zulu is the only 'named' timezone we support (from checking source
CREATE FUNCTION ... SECURITY DEFINER;
Read the 7.3 docs.
Chris
Telecontrol Networking wrote:
Hi,
I really need that a FUNCTION runs allways with this creator/owner
permissions, and not with the user permission.
In other words, my FUNCTION must execute several procedures as POSTGRES
superu
refering to my math professor thats wrong, at least in germany.
select round(2.5); should return 3
Well, I thought mathematics theory says that you should round to the
nearest even number for a 0.5 value, so as to avoid biasing your data...?
I just tried that on my 7.2.4 and 7.4 beta 4 machines
I should mention that I don't have access to a FreeBSD Alpha box anymore
:( Hence, I have no idea if it currently compiles or not.
Chris
Peter Eisentraut wrote:
Bruce Momjian writes:
It is time for people to report their port testing. Please test against
current CVS or beta5 and report your
The latter...why won't it affect the postmaster state?
Because it's a *comment*.
Shouldn't it revert to the default value?
Chris
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
By "disable" do you mean "turn off", or "comment out again"? The latter
is not going to affect the state of the postmaster ...
The latter...why won't it affect the postmaster state?
Chris
---(end of broadcast)---
TIP 6: Have you searched our list
If you don't use -w, then pg_ctl doesn't wait around to see whether the
postmaster started or not. It'd probably be a good idea for it to issue
a less positive message in this case, maybe only "postmaster launched".
I also wonder why -w isn't the default.
I've also noticed that on our production 7
You couldn't have said better what I meant.
I store the xml already parsed. You can navigate right along. To the
parent, the previous, the next elemnt or the first or last child.
Which is the whole point of indexing it...
I use XML a lot for all sorts of purposes, but it is appropriate for
data tr
4. Extend the contrib/ltree gist-based tree indexing scheme to work on
xml and hence the operations in no.3 above are really fast...
but then, the plain xml data is still stored in a database colum, if I
understand correctly?
Yep - which to me seems to be the most useful way to store it :)
Chris
Is it worth mentioning this as a compatibility issue?
"Prior to PostgreSQL 7.3, serial implied UNIQUE. This is no longer
automatic. If you wish a serial column to be in a unique constraint or a
primary key, it must now be specified, same as with any other data type."
Er, that *was* a compatibi
Is it worth mentioning this as a compatibility issue?
"Prior to PostgreSQL 7.3, serial implied UNIQUE. This is no longer
automatic. If you wish a serial column to be in a unique constraint or a
primary key, it must now be specified, same as with any other data type."
Chris
---
Do this:
1. Create a new type called 'xml', based on text.
2. The xmlin function for that type will validate what you are
enterering is XML
3. Create new functions to implement XPath, SAX, etc. on the xml type.
4. Extend the contrib/ltree gist-based tree indexing scheme to work on
xml and hen
I see you're point, but nobody is going to be interested in the first 2
billion rows of a table without using a cursor and having some other
process do the math in the background.
You have the same problem:
test=# begin;
BEGIN
test=# declare c cursor for select * from a;
DECLARE CURSOR
test=# move
'allballs' probably alludes to the visual appearance of '00:00:00'. 'z'
and 'zulu' should be time zones equivalent (or similar?) to UTC or GMT
((US?) military jargon).
Why do we support just 'zulu' and none of the other magic time zone names:
http://wwp.greenwichmeantime.com/info/timezone.htm
C
What in the heck is 'zulu', 'allballs' or 'z'???
'allballs' probably alludes to the visual appearance of '00:00:00'. 'z'
and 'zulu' should be time zones equivalent (or similar?) to UTC or GMT
((US?) military jargon).
But they don't work...
Chris
---(end of broadcast)-
Hi guys,
What is the limit on the number of rows in a PostgreSQL table? If it's
more than MAXINT, we have a problem:
phppgadmin# select * from test limit 2147483648;
ERROR: integer out of range
Same problem with OFFSET.
Chris
---(end of broadcast)---
What does this in the date/time type docs mean?
zulu, allballs, z time 00:00:00.00 UTC
Cos it has bizarro behaviour:
In 7.3.4:
australia=# select 'zulu'::time;
ERROR: Bad time external representation 'zulu'
australia=# select 'allballs'::time;
time
--
00:00:00
(1 row)
australia=# s
A moment's further thought reveals 'today' as another potentially broken
default value, which seems more likely to be used in practice than
'yesterday' or 'tomorrow'. I'm too beat to go digging for other legal
inputs, but there may be some...
Ah, I didn't mention that one because I thought it wa
It would be pretty strange to use those as a default --- I am not
inclined to mention it in the release notes --- we don't mention every
change, only significant ones.
Personally, I think that's a fairly silly policy! How does it hurt us
to mention it and you just know that someone, somewhere, i
Now that DEFAULT 'now' will not work in PostgreSQL 7.4, will DEFAULT
'infinity' and DEFAULT '-infinity' and the like stop working as well?
No, because those values don't change over time. The issue here is when
exactly does the default value get evaluated...
Ah, of course - but what about 'y
Hi,
Now that DEFAULT 'now' will not work in PostgreSQL 7.4, will DEFAULT
'infinity' and DEFAULT '-infinity' and the like stop working as well?
What is the workaround for those defaults?
Chris
---(end of broadcast)---
TIP 8: explain analyze is yo
We now have another reason to, which is Chris K-L's point about
unqualified names in the various SQL-language built-in functions.
I am about to commit that fix (with another catversion bump for
good measure...)
Oh dear. We really need this function-specific schema path that the SQL
standard seem
There is always the biggest evil of all... Putting SHOW / DESCRIBE /
HELP commands into the backend itself. I'm sure the pgAdmin group likes
that idea (they're probably tired of maintaining 4 different versions of
queries for getting a list of tables). Any solution to make psql
backward or forward
There is always the biggest evil of all... Putting SHOW / DESCRIBE /
HELP commands into the backend itself. I'm sure the pgAdmin group likes
that idea (they're probably tired of maintaining 4 different versions of
queries for getting a list of tables). Any solution to make psql
backward or forward
ly do names from pg_catalog.
Chris
Christopher Kings-Lynne wrote:
How do I use a schema-qualified name in obj_description? Or is this a
nsty little bug?
Chris
test2=# create schema myschema;
CREATE SCHEMA
test2=# create table myschema.pg_class (a int4);
CREATE TABLE
test2=# select oid
How do I use a schema-qualified name in obj_description? Or is this a
nsty little bug?
Chris
test2=# create schema myschema;
CREATE SCHEMA
test2=# create table myschema.pg_class (a int4);
CREATE TABLE
test2=# select oid from pg_catalog.pg_class where
oid='myschema.pg_class'::regclass;
oid
-
I suppose if all you want is backward compatibility which makes sense
for pg_dump, but surely psql should be forward thinking.
>
Normally it's old clients with new server, not the other way around --
at least with big companies it seems easier to get a server upgraded
than everyones desktop.
Forwar
The tricky part seems to be dealing with i10n issues since the text to
translate would be release specific it needs to go into the backend --
but that isn't so nice.
Why tricky? I'm just going to make the 7.5 psql utility work against
previous versions of postgresql. Any strings in that utility
I feel like looking into it, but tell me if I'm wasting my time...
Please do ...
I wonder what would it take. It only needs a different set of queries
to obtain info from the syscatalogs, or is it more involved?
Looks fairly straightforward to me. Just need to get backend version
out. Maybe
Hi,
Is there demand for modifying psql to work against previous backends,
pg_dump-style?
I feel like looking into it, but tell me if I'm wasting my time...
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PR
What about bumping the libpq version?
Chris
Marc G. Fournier wrote:
Just a quick note that we'd like to wrap up a Beta5 during the day
tomorrow, based on all the changes since Beta4 ... is anyone sitting on
any patches that postponing it "just one more day" would help ... ?
--
I noticed that the function to get max builtin OID for 7.0 does this:
template1=> SELECT oid from pg_database where datname = 'template1';
oid
---
17216
(1 row)
However, that is incorrect:
template1=> select oid,relname from pg_class where oid > 17216;
oid | relname
---+---
o Add SET SCHEMA
What is this supposed to do (and how's it different from SET SEARCH_PATH)?
I believe someone thought it was the SQL standard way of doing it.
Probably needs to be checked though.
Chris
---(end of broadcast)---
TIP 6: Have you
True. Btw., is there a particular value in pg_get_constraintdef always
printing double pairs of parentheses for CHECK constraints?
No, but it will require some restructuring of the code to get rid of it
safely (where "safely" is defined as "never omitting any parentheses
that *are* necessary").
I looked through all the information_schema stuff, and found a few more
nits.
I notice that most of the references in the information_schema.sql are
not schema-qualfied.
eg:
FROM (pg_namespace ncon INNER JOIN pg_constraint con ON ncon.oid
Shouldn't that be:
FROM (pg_catalog.pg_namespace ncon I
Is it just me or does pg_dump have no support for dumping conversions at
all?
conversions=# CREATE CONVERSION myconv FOR 'UNICODE' TO 'LATIN1' FROM
alt_to_iso;
CREATE CONVERSION
conversions=# \q
bash-2.05a$ /home/chriskl/local/bin/pg_dump conversions
--
-- PostgreSQL database dump
--
SET SESSIO
regression=# select oid from pg_cast;
oid
---
16420
16421
16422
16423
16424
... etc ...
It would be a very serious design error if pg_cast didn't have OIDs,
because then pg_cast entries couldn't have dependency entries in
pg_depend.
OK. Weird. I could have _sworn_ I tried that and I d
I just noticed this fairly silly behaviour:
test=# select to_char(current_date, 'D'), extract(dow from current_date);
to_char | date_part
-+---
3 | 2
(1 row)
I guess we can't change that now, but they really should number their
days from the same base...
Chris
Hey guys,
Is it true to say that it's impossible for me to allow comments on
casts, as there is no OID on the pg_cast table?
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Changes
---
Allow superuser (dba?) the ability to turn off foreign key checks/all
constraints/triggers, not settable from postgresql.conf?
Is that one really necessary for 7.4 now that adding foreign keys is
apparently much faster?
Chris
---(end of broadcast)
Hi guys,
For formatting types pre-7.1, how do I know what the value of VARHDRSZ
is? (Given that it's a PHP script, say.)
I need to be able to subtract that from the typmod to get the field length.
Is it possible?
Chris
---(end of broadcast)---
TI
Unimplemented feature AFAIR. BTW, if you feel like doing something
about this, COMMENT ON LARGE OBJECT would be good too.
* COMMENT ON [ CAST | CONVERSION | OPERATOR CLASS | LARGE OBJECT ]
Bruce - want to make this a TODO? May as well assign it to me - I'll
have a play with it. I assume th
I notice you cannot COMMENT ON the following:
* Cast
* Conversion
* Operator class
Is that a deliberate omission, or is it an oversight?
Unimplemented feature AFAIR. BTW, if you feel like doing something
about this, COMMENT ON LARGE OBJECT would be good too.
* COMMENT ON [ CAST | CONVERSION | O
Well, this is really embarassing. I can't imagine why we would not set
at least -O on all platforms. Looking at the template files, I see
these have no optimization set:
freebsd (non-alpha)
I'm wondering what that had in mind:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/temp
1001 - 1100 of 2140 matches
Mail list logo
