any many more complaints, as is a rather
common name for constraints :).
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
ner:
> > chriskl
> > --
> >
> > SELECT pg_catalog.setval ('users_users_userid_seq', 126, true);
> >
> >
> > How do we fix this problem?? Perhaps instead of a hard-coded sequence
> > string, we can sub-SELECT for it...?
> >
> > Chris
> >
> >
> >
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
d absolutely nothing to do
with 2 phase commits -- but were used as a marker to direct replication.
We may want to consider leaving some space for a server / server style
communication (Cluster ID, etc.)
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Desc
ack to old protocols easily enough for the future so that we can do
incremental changes to the protocol.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Mon, 2003-03-10 at 14:30, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I'd be tempted to make a startup packet that will allow libpq to revert
> > back to old protocols easily enough for the future so that we can do=20
> > incremental changes
On Mon, 2003-03-10 at 14:52, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> >> We already have that: you send a startup packet with a version less than
> >> the latest, and the backend speaks that version to you.
>
> > Yes, but that requires y
mple) text near to impossible
because of this.
> Is it practical/desirable for PostgreSQL to have this as a configuration
> setting?
I think we already support this. Create a new character set with upper
/ lower case specified as being equal and PostgreSQL should behave as
expected.
--
Rod Tayl
ower('BLah');
>
> That would probably require an extra index, especially if 'field' is a
> primary key.
I don't know about MSSql, but on MySQL you also require a different
index for a case sensitive comparison. Problem is, they don't (didn't)
supp
the list who could
answer this definitively.
> Rod Taylor wrote:
>
> >On Wed, 2003-03-12 at 12:57, [EMAIL PROTECTED] wrote:
> >
> >
> >>>--le 12/03/2003 09:03 -0500, mlw écrivait :
> >>>| I was at a client office reviewing some code. They use MSSQL and
only picked implode() because
> that's what it is called in PHP. Any suggestions?
I think implode() and explode() go together. split() and join() are a
pair. Pick one ;)
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
like to see it in 7.4, so if it doesn't look like you'll
be done in time, feel free to ask for a hand.t
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
ppear
after that.
Enforcing spec seems like the least confusing mode to operate under,
especially given it could break simply by changing the plan -- which
happens automagically (seemingly random).
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
or valuntil to be
'infinity'. NULL implies they will expire, we're just not sure when.
Infinity shows that we do not intend to expire the user -- which is more
in-line with the actual implementation.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
nce between them?
>
> Thanks a lot.
>
> Jinqiang Han
>
>
>
>
>
> ---(end of broadcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
--
Rod Tayl
ply evaluate the default value -- which should be easily
retrievable and more portable in most interfaces (jdbc, odbc, etc.).
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
ection 6.5).
> >
> > In other words, this syntax should be legal:
> >
> > UPDATE sometable SET somecolumn = DEFAULT;
> >
> > but it doesn't appear to be implemented as of CVS tip.
>
> Hmmm...I ran into a situation where I wanted that just the other day.
&g
table / column that the sequence (SERIAL)
is on. This would hide the internal representation of a SERIAL...
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
now...)
I do -- but the only thing it does is format the output to look better.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
of code I have written that I would need to implement it.
>
> Is there any sort of philosophical problem with that?
There is a big difference between an LGPL'd library and a GPL'd library.
The latter may have problems as I believe your code should be GPL'd, but
the former sho
Is there an easy way of doing this? Insert was simple as all that
needed to be done was to throw away the reference to the column.
It would seem a new primnode (change InsertDef into SetDefault or
similar) will be required with some executor logic.
--
Rod Taylor <[EMAIL PROTECTED]>
P
tion of items such as the ON
UPDATE or ON DELETE type (statement parsing is required), but the
information schema gives the information in a segregated manner.
The pg_get_*def() functions seem to have been created primarily for psql
and pg_dump.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key:
Incase someone is interested, here is a patch without the CURRENT VALUE
FOR portion.
On Sat, 2003-05-24 at 23:39, Rod Taylor wrote:
> We need to track sequence usage in things like defaults. nextval()
> function calls don't easily allow this to happen.
>
> The 200N spec has N
(aside from 'Warning').
DB2 seems to use an SQLCode (Chapter 11) which catalogues all of the
error messages, the error code, and SQLState applied to it.
The entire book has to do with DB2 messages and their meaning.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca
le-driven form,
> but AFAIR he didn't have a satisfactory answer.
I've yet to come up with anything better. Best answer I've come up with
is to make the column headings a separate query result set and let the
back-end do the translations.
--
Rod Taylor <[EMAIL PR
TO newname;
ALTER TABLE
test=#
test=# \d test
Table "public.test"
Column | Type | Modifiers
-+-+---
newname | integer |
Check Constraints:
"test_col" CHECK (col > 2)
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.
On Mon, 2003-06-02 at 14:00, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > As you can see below, after a rename the check constraint still refers
> > to 'col' and not 'newname' as pg_constraint.consrc is not updated.
>
> T
=# set time zone est;
SET
rbt=# select * from t;
col
2003-06-03 18:30:25+00
(1 row)
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Wed, 2003-06-04 at 14:55, Christopher Browne wrote:
> Rod Taylor wrote:
> > Note the first timezone change is taken, but the second one is ignored.
> > rbt=3D# set time zone est;
> > SET
> > rbt=3D# select * from t;
> > col
> > -
ok at it for the next.
> (He's on holiday for the next few days btw which is why I'm chiming in)
I see.. Thanks.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
> 4) Does anyone else have any comments on the proposed re-ordering?
Since we're painting a shed, does it make sense to put the items in
alphabetical order for each section?
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This
ase cc: any comments directly to me!
You re-subscribed I assume...
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Thu, 2003-06-05 at 16:45, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > It would seem a new primnode (change InsertDef into SetDefault or
> > similar) will be required with some executor logic.
>
> It is not the executor's business to know about
> So are we eliminating the autocommit GUC entirely, or just from
> postgresql.conf?
It's a client side feature now. Completely gone from the server.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
eebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup-docbook.html
Gnome Doc Project, intro to Docbook:
http://developer.gnome.org/projects/gdp/handbook/gdp-handbook/ar01s04.html
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
plementation
of adddepend, which is also used in a few other well used programs.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
or two out of it.
But it is much easier to change the internal structures now, as
PostgreSQL doesn't have nearly as much of a backward compatibility issue
anymore.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
ude/libpq/libpq-be.h:22,
from ../../../../src/include/libpq/libpq.h:21,
from printtup.c:20:
../../../../src/include/libpq/pqcomm.h:50: redefinition of `struct
sockaddr_storage'
gmake[4]: *** [printtup.o] Error 1
--
Rod Taylor <[EMAIL PROTECTED]>
CK_TYPES([struct sockaddr_storage], [], [],
[#ifdef HAVE_SYS_SOCKET_H
#include
#endif
])])# PGAC_STRUCT_SOCKADDR_STORAGE
On Thu, 2003-06-12 at 09:30, Rod Taylor wrote:
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -g -Wall
> -Wmissing-prototypes -Wmissin g-declarations -I../../../..
> > We could change
> > float8/i.86-.*-freebsd=float8-small-is-zero
> > to
> > float8/i.86-.*-freebsd4=float8-small-is-zero
This change compiles / regresses fine for me, but I didn't read the
whole thread to try to see what to look for.
--
Rod Taylor <[
ch contains comments. They would
then be dumped back out to the user.
But I think you would be dissapointed if you were returned the view that
is no longer correct since someone renamed the tables.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
errors on a
standard ./configure, but if I run ./configure --with-threads there are
no errors and everything runs fine.
I'll check a little more into it.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
able to do a datatype
change safely.
http://candle.pha.pa.us/main/writings/pgsql/sgml/catalog-pg-cast.html#AEN49071
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
/misc. (Not that
> > that name seems very compelling either...)
>
> We could call it tools or admintools.
How about just pulling them up a directory into src/bin?
If they were complex, each would have a subdirectory in src/bin, so it
seems reasonable to have individual files there.
ence for developers using PostgreSQL (reduces
chance of rare, unexpected, and difficult to find logic errors).
If nothing else, it makes for an excellent cleanup release that rounds
off some of the sharp corners (tab completion for schema elements in
psql, schema dump in psql, fixed cluster support, tra
space, as if the user did those
items as individual commands within the same transaction. Someone can
make it more efficient in regards to constraint checks, etc. in the
future if they want -- I don't intend to.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
ificant reorganization
of the ALTER TABLE functions (or lots of duplicated code), but shouldn't
be that time consuming.
Anyway, I suppose you have indirectly confirmed that user triggers, etc.
should NOT fire on for the data update. I didn't see anything in the
spec that said one way or
On Thu, 2003-06-19 at 09:40, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > Anyway, I suppose you have indirectly confirmed that user triggers, etc.
> > should NOT fire on for the data update. I didn't see anything in the
> > spec that said one wa
On Thu, 2003-06-19 at 10:05, Alvaro Herrera wrote:
> On Thu, Jun 19, 2003 at 09:52:14AM -0400, Rod Taylor wrote:
> > On Thu, 2003-06-19 at 09:40, Tom Lane wrote:
>
> > Do we want them to? If we don't mind them being executed, it is far
> > easier to:
> >
&g
't fire.
Sounds like a definitive answer to me. I'll go that route then.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
new and
unexpected issues.
Tracking down several users for windows testing is a good idea. Rushing
it out in an unknown state to get the testing isn't such a good idea in
my mind.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This
On Thu, 2003-06-19 at 10:42, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > On Thu, 2003-06-19 at 10:05, Alvaro Herrera wrote:
> >> Sorry, I haven't read the spec, but what happens when there is a default
> >> value already and it's not
On Thu, 2003-06-19 at 15:00, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > Right now if the column exists in the child table, the add column is
> > rejected. I assume that will remain.
>
> Have you actually tried it?
I used different datatypes which, of
of not requiring a vacuum.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
een
since there is not a method of controlling the timing at the moment.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
en't ready to be committed at the time, nor are they now.
The hardest parts are still to come (resume, forget, etc.).
I believe he is still working on the third phase:
http://snaga.org/pgsql/
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
De
tgreSQL has a choice in the matter -- like
communication with other PostgreSQL servers.
This is a case of learning to speak Japanese because all of the people
you want to talk with only speak Japanese. It simply doesn't matter how
good Esperanto is.
--
Rod Taylor <[EMAIL PROTECTED]>
PG
e jumping up and down
when they get them, myself included.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
> Oh, one more thing --- right justify isn't as accepted as left-justify
But it looks so much better...
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
er_table AS yat
ON (yat.c = tab.c)
LEFT JOIN tab1 USING (anothercol)
WHERE stuff IS TRUE
AND ( optional IS NULL
OR optional > 5)
HAVING count(*) > (SELECT total
FROM total_table)
ORDER BY foo
GROUP BY foo
, bar
, 3;
--
Rod Tay
c:272: for each function it appears in.)
misc.c: In function `ECPGis_informix_null':
misc.c:330: `LONG_LONG_MIN' undeclared (first use in this function)
gmake[4]: *** [misc.o] Error 1
gmake[4]: Leaving directory
`/usr/home/rbt/work/postgresql/pgsqlwarning/src/interfaces/ecpg/ecpglib&
> Anyway, if you have and it appears you also have HAVE_LONG_LONG_INT_64
> defined, which header file does provide the approprioate constants and
> how is it named? It seems INT_MIN etc. are there.
/usr/include/machine/limits.h seems to have INT_MIN, etc. in them.
--
Rod Taylo
rlier fix.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Thu, 2003-06-26 at 15:00, Austin Gonyou wrote:
> I know I'm new to this list, but is OSDL's testing capabilities out of
> the question?
From what I've seen, OSDL is only concerned with a very very small set
of platforms (Linux in a couple of configurations).
--
Rod Tay
a few volunteers to cron the script (I'll volunteer).
I think we should replace Bruce's pgtest script with this one -- with an
argument to accept the email address to report to for FAILING cases.
Success isn't very interesting if it runs regularly.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
ty of PostgreSQL benchmarks to choose from. Adding a regression
test for performance would be a wise thing to do, but will require
dedicated hardware for good numbers (especially if run nightly).
Thomas had a good start in mind. Hopefully we can extend it a little
once it has been started.
--
Ro
t the time), but there are some
circumstances that may cause the binary column to be irretrievable due
to a corrupt system catalogue -- which is still possible despite
dependencies (concurrency issues -- lack of object locking).
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/r
old database.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
:59, Peter Eisentraut wrote:
> Rod Taylor writes:
>
> > psql:22.sql:2324: ERROR: dependent privileges exist (use CASCADE to
> > revoke them too)
> >
> > Line 2324 is:
> > REVOKE ALL ON TABLE sh2bill_action_action_id_seq FROM rbt;
> >
> > This user was
ROUPING SETS
::=
[ { }... ]
::=
::=
|
|
|
::=
|
::=
::=
[ { }... ]
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
I just noticed that the OSDL benchmarks for PostgreSQL appear to require
PostgreSQL be compiled with INDEX_MAX_KEYS as 64 rather than the default
of 32.
Any chance the default could be bumped for the 7.4 release?
Does it cause a significant performance issue?
--
Rod Taylor <[EMAIL PROTEC
On Tue, 2003-07-01 at 01:25, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I just noticed that the OSDL benchmarks for PostgreSQL appear to require
> > PostgreSQL be compiled with INDEX_MAX_KEYS as 64 rather than the default
> > of 32.
>
> Which
iece of code (more proof of concept than production).
If I'm not mistaken, the request was that you and Joe would merge the
code with standard dblink and integrate both into the backend for 7.5.
http://fts.postgresql.org/db/msg.html?mid=1504725
--
Rod Taylor <[EMAIL PROTECTED]>
PGP
Moving to -hackers.
> In my opinion the defaults should be set up for a typical database server
> machine.
Ok.. thats fair. The first problem would be to define typical for
current PostgreSQL installations, and typical for non-postgresql
installations (the folks we want to convert).
After that,
On Tue, 2003-07-08 at 21:31, ivan wrote:
> What do you think about :
>
> 1. OPTION RETURNS NULL ON NULL INPUT (when function is created) change to
> RETURNS ON NULL INPUT ???
I personally think this should be up to the specific function to
capture. This way it could be a complex result.
On Thu, 2003-07-10 at 02:28, Christopher Kings-Lynne wrote:
> How's this for an idea? We release a statically compiled version of pg_dump
> (from the 7.4 tree say) that is able to dump 7.3, 7.2 databases etc. We
> recommend to people that they use that to dump their existing database?
Out of cur
> Hm. Evidently not :-(. The COMMENT ON DATABASE facility is a bit bogus
> anyway (since there's no way to make the comments visible across
> databases). You might be best advised not to use it.
>
> Hackers: this seems like an extremely bad side-effect of what we thought
> was a simple addition
> 3. Ignore the specified DB name, store the comment as the description
>of the current DB; possibly give a warning saying we're doing so.
>This would allow correct restoration of dumps into different DBs,
>but I think people would find it awfully surprising :-(
I like this one for 7.4
> Is this really a good thing to do? Is it part of the standard? Can it be
> turned of? In my case it hid a bug and made my query work but produce the
> wrong result.
7.4 has a switch to turn this off for the same reasons you cite.
signature.asc
Description: This is a digitally signed message pa
On Wed, 2003-07-16 at 21:16, Tom Lane wrote:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > Is the patches list working?
>
> I saw something come through yesterday from Rod.
Which is funny because it's not in the archives and I didn't receive the
message to my own inbox.
signature.asc
Descrip
> For COMMENT ON DATABASE where database name is unknown or not the current
> database, emit a WARNING and do nothing, rather than raising ERROR.
> Per recent discussion in which we concluded this is the best way to deal
> with database dumps that are reloaded into a databas
On Fri, 2003-07-18 at 19:46, Paulo Scardine wrote:
> My boss is asking for something like Oracle's "SELECT FOR UPDATE NOWAIT".
>
> Is there any such feature? If no, should I look forward into implementing
> this? Any advice?
Lookup STATEMENT_TIMEOUT and set it to a very short time.
signature.as
> Another good reason for per-database directories under the tablespace is
> to prevent directories from containing too many files.
Actually, I would take that as an reason not to have database
directories.
If the number of files becomes a concern, we would need some kind of a
hashing algorithm t
> I don't see the problem.
How about a (simple!) configure process in the dblink directory only
which detects the various items.
signature.asc
Description: This is a digitally signed message part
On Tue, 2003-07-22 at 09:06, Merlin Moncure wrote:
> I looked on the to-do list and noticed adding check constraints to
> domains is not on it. IMO, being able to add a validation constraint
> is one of the very best things about domains. Is anybody planning to
> work on this?
7.4 has descent
> > Won't that break when we have nested transactions implemented? i.e.
> > begin;commit; would just open a sub transaction and have no effect on the
> > outer transaction...
>
> Yes, it would break. I am not sure how we are going to flag that we
> want to rollback all nested transactions, may
On Thu, 2003-07-24 at 02:45, Sailesh Krishnamurthy wrote:
> > "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> Tom> That doesn't work, unless you insist that the first backend
> Tom> can't exit its transaction until all the other ones are done.
> Tom> Which introduces its own poss
> Better remove transactions then, yeah? Performace hit! Profile it and
> see how minor (or likely non-existent) it is...
You can do that. Turn fsync to off and you remove a large majority of
the transaction hit, but I understand what you're saying.
signature.asc
Description: This is a digitall
On Tue, 2003-07-29 at 09:50, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Then why did we add a GUC variable "server_encoding" at all?
>
> The JDBC guys wanted to know it. Why is not clear to me, but I figured
> it was easy enough to make them happy.
It could still be usefu
On Tue, 2003-07-29 at 21:45, Christopher Kings-Lynne wrote:
> Hi guys,
>
> I hear that we're supposed to use the 'bin' versions of the 'src' columns
> where possible. I would like then to use them in phpPgAdmin for displaying
> defaults and stuff. Is there some way to use them from SQL? Cos it a
On Fri, 2003-08-01 at 20:32, Mark Wong wrote:
> On Fri, Aug 01, 2003 at 05:05:18PM -0700, Josh Berkus wrote:
> > Mark,
> >
> > > I've just got our DBT-2 workload (TPC-C derivate) working with
> > > PostgreSQL using C stored functions and libpq. I'd love to get some
> > > feedback.
> >
> > I'm co
Moving to -hackers
> I'm working on getting auto-incrementing CMP fields in JBoss 3.2.1 to
> work with PostgreSQL data sources. There are currently two obstacles
> to this.
Yeah.. JBoss is very annoying in this regard. A temporary solution seems
to be to use BEFORE triggers to force the sequence
On Sat, 2003-08-02 at 17:19, Carlos Guzman Alvarez wrote:
> Hello:
>
> I continue to be working in my .NET Data provider for postgres 7.4, i
> want to know if there are a simple way for identify autoincrement
> fields, i see that for serial and big serial fields the default value is
> 'nextval(
> des=# create table test ( id serial, word text );
> NOTICE: CREATE TABLE will create implicit sequence "test_id_seq" for SERIAL column
> "test.id"
> CREATE TABLE
> des=# create rule test_id_generate as
> des-# on insert to test do instead
> des-# insert into test ( id, word ) values ( default,
> On the other hand, I seem to have botched the definition of
> force_default_value() in include/catalog/pg_proc.h, because adding the
> trigger manually doesn't seem to work either:
>
> | des=# \df force_default_value
> | List of functions
> | Result data type | Sc
On Sun, 2003-08-03 at 10:31, Dag-Erling Smørgrav wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I think a longer term solution would be to add a type to pg_attrdef and
> > a bool for ALWAYS. (Tom?)
>
> I thought about it, but won't that change the on-dis
On Sun, 2003-08-03 at 14:35, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > Yes it would. The solution you have already requires an initdb (changed
> > pg_proc.h), as such will probably need to wait until 7.5 for
> > integration. You might be able to squeez
> Truncate isn't transaction safe either, so that shouldn't be a problem.
Actually, it is in 7.4
> Proper syntax for his feature would seem like:
> truncate table [cascade|restrict] ?
Agreed.
signature.asc
Description: This is a digitally signed message part
On Mon, 2003-08-11 at 19:16, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > rbt=# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
> > ERROR: syntax error at or near "ALL" at character 32
> > rbt=# ALTER USER rbt SET CONSTRAINTS = DEFERRED;
> >
The below function works in 7.3 (returns nothing, but no errors).
rbttest=# begin;
BEGIN
rbttest=# create or replace function service.test(integer)
rbttest-# returns setof service.service
rbttest-# as '
rbttest'# declare
rbttest'# v_service service.service%rowtype;
rbttest'#
rbttest'# begin
rb
On Fri, 2003-08-08 at 16:00, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Seems we have a problem with pooled connections and WITH HOLD cursors.
> > We have code to reset transaction state and variables via RESET ALL, but
> > how do we remove WITH HOLD cursors when we pass a conn
501 - 600 of 994 matches
Mail list logo
