as
well as changes unique indexes into unique constraints.
As I had a few items I didn't want to upgrade, it asks the user if they
want to do each one (-Y to fix 'em all).
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you che
ental use, and does
> allow pg_xlog moving without symlinks, which some people don't like?
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
ttp://www.rbt.ca/postgresql/upgrade.shtml
Doesn't deal with DEFERRED triggers.
--
Rod Taylor
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
)
INSERT INTO (...) VALUES (...) will not allow you to skip value entries,
but the keyword DEFAULT is available now, so it shouldn't be much of an
issue.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Mon, 2002-09-16 at 17:54, Tom Lane wrote:
> In CVS tip:
>
> regression=# create domain nnint int not null;
> CREATE DOMAIN
Ok, I'll take a look at this today.
Thanks
--
Rod Taylor
---(end of broadcast)---
TIP
x27;s not all unique, you cannot be guaranteed there is a single row
with those values in the referenced table.
--
Rod Taylor
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
tn't change any data.
> What if function change data in from clause ?
Why can't the function change data? I've done this one a number of
times through views to log the user pulling out information from the
system, and what it was at the time (time sensitive data).
--
Rod Taylo
s
closed at transaction commit, and re-created in next use.
4.29:
For every in an SQL-client module, a cursor is
effectively created when an SQLtransaction (see Subclause 4.32,
SQL-transactions ) referencing the SQL-client module is initiated.
--
Rod Taylor
--
> All the problems here are coming from INSTEAD rules. We don't have
> INSTEAD triggers or contraints.
Well.. Triggers could be exclusively INSTEAD. A trigger could easily
write a few things to a number of other tables, and return NULL in a
BEFORE trigger which would prev
oes not exists
> snpe> select * from org_ban;
> ERROR: current transactions is aborted, queries ignored until end of
> transaction block
> snpe> rollback;
> ROLLBACK
> snpe> select * from org_ban;
Maybe I'm missing something, but isn't that
for progress.
However, rest assured, with anything if you push and put in the work
require it'll eventually go where you want it to.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ks for *all* software. If you never release, nothing gets
better.
I suspect it'll be several more major releases before we begin to
consider it approaching completely functional.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ecessary.
Indeed, if you delete the dependencies, then drop the column the view
continues to function but I'm not sure thats always the case.
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.po
hich explains
all of the 0.9's.
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Fri, 2002-09-06 at 01:19, Christopher Kings-Lynne wrote:
> OK,
>
> The argument about using ALTER TABLE/ADD FOREIGN KEY in dumps was that it
> caused an actual check of the data in the table, right? This was going to
> be much slower than using CREATE CONSTRAINT TRIGGER.
>
> So, why can't we
a
bunch of requests.
On Thu, 2002-09-05 at 21:37, Christopher Kings-Lynne wrote:
> Whoot! I was just thinking about writing such a tool. Thanks.
>
> Chris
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Rod T
In the process of upgrading a few systems for the Beta, I ended up
writing a tool to upgrade the Foreign key, Unique, and Serial objects to
their 7.3 version from the 7.2 version (may work on prior -- but not
guarenteed).
I imagine it'll fail miserably on mixed case, or names with spaces --
but o
On Thu, 2002-09-05 at 11:19, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > SunOS control.shared2 5.7 Generic_106541-20 sun4u sparc SUNW,Ultra-5_10
> > shows an error in ALTER TABLE tests:
>
> > ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1)
On Wed, 2002-09-04 at 22:39, Marc G. Fournier wrote:
>
> will announce it on -announce tomorrow, if ppl want to take a quick look
> at it ... man pages weren't included, but I did regenerate the docs per
> Peter's suggested commands ...
'./configure && make check' passes on i386 FreeBSD.
SunOS
It would be far simpler to put each of the core teams names on the top
of the history file in big bold letters -- or perhaps a watermark in the
background ;)
> While we're competing for the humble award, you might want to add Tom to
> that list...
---(end of broadcast)-
Found this line without a name:
Propagate column or table renaming to foreign key constraints
Is that item complete? pg_constraint follows (as such dump / restore
will work) but the triggers themselves still break, don't they?
On Wed, 2002-09-04 at 03:24, Bruce Momjian wrote:
> OK, the HISTORY
On Tue, 2002-09-03 at 16:42, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > DEBUG: server process (pid 9097) was terminated by signal 10
>
> Could we have a backtrace from that core dump?
>
> AFAICT it's getting through the WAL redo just fine, so
Seems it wants to run a redo entry that doesn't exist.
Not a big deal as it's a test environment only. It was recently
upgraded from 7.2.1 to 7.2.2. I'm wondering whether the person who did
the upgrade shutdown the daemon before installing.
FATAL 1: The database system is starting up
FATAL
On Tue, 2002-09-03 at 11:01, Tom Lane wrote:
> "Shridhar Daithankar" <[EMAIL PROTECTED]> writes:
> > 1)Is this sounds like a workable solution?
>
> Adding a trigger to every tuple update won't do at all. Storing the
> counts in a table won't do either, as the updates on that table will
> generat
On Tue, 2002-09-03 at 03:36, Mario Weilguni wrote:
> > gets updated for each transaction but log table is just an insert. So
> rather
> > than vacumming entire db, just doing 'vacuum analyze accounts' give me
> almost
> > same results.
> >
>
> That is not really practicable, one datebase has 107
> > * Have SERIAL generate non-colliding sequence names when we have
> > auto-destruction
> >
> > They should be pretty well non-colliding now. What's the gripe exactly?
>
> The issue was that when there were name collisions, we threw an error
> instead of trying other sequence names. We h
On Mon, 2002-09-02 at 02:36, Christopher Kings-Lynne wrote:
> Whatver happened to Rod's work on the BETWEEN command? I remember he got to
> the stage of realising a lot of execetor changes had to be made...?
I've not had time to implement the optimizer portion.
---(end
> Oops, my fault for being imprecise.
>
> I was wondering what time of day with timezone. Someone suggested end of today
> but that means different times to different people.
This is what Marc said yesterday:
Yup, I believe that it is the case that both the US and Canada
"celebrate"
labour day
> One more idea, is it possible to "fake" a read-write file system. I.e.
> supply the files that postgresql will be looking for? (I know it's a
> stretch, but hey, this IS the "hackers" list) :)
One of the tricks I use for diskless systems is to mount a ramdrive in a
union mount with a read on
> Yes, I thought about that. People want to show both SELECT syntaxes,
> but how would you do that --- show the SELECT syntax twice with just
> those last two clauses reversed --- yuck.
select [ , ... ]
:
[ FOR UPDATE | LIMIT ]
The above, or something along those lines, would show o
On Wed, 2002-08-28 at 10:24, Robert Treat wrote:
> On Wed, 2002-08-28 at 10:11, Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Larry Rosenman wrote:
> > >> Why? If both old and new are acceptable, why not document it?
> > >> (Just curious, I'm not wedded to it).
> >
> > > W
> > A settable trim length would probably be a good idea, I suppose, for
> > those slinging 'bytea' and toasted texts around.
> Yes, but the default should be NO TRIM or in 1K-4K range. IMHO
Ditto.
---(end of broadcast)---
TIP 1: subscribe and un
On Tue, 2002-08-27 at 16:54, Bruce Momjian wrote:
>
> I had an idea on this. It seems pretty pointless to show a query error
> without a query, but some queries are very large.
>
> How about if we print only the first 80 characters of the query, with
> newlines, tabs, and spaces reduced to a si
It should also be noted that it's easy to get the DBAs to change their
username in the future when / if the @ hack goes away BUT it will be
difficult to change the usernames of the hundreds to thousands of
customer accounts.
For an upgrade, we'd end up making a script in the upgrade to keep them
o be the holding area for those otherwise without a home.
> -------
>
> Rod Taylor wrote:
> > Mostly because a user may explicitly create a database with wanted
> > permissions, only to have this 'spe
Mostly because a user may explicitly create a database with wanted
permissions, only to have this 'special code' remove them.
I personally intend to immediately revoke permissions on public in
template1, to allow the database owner to grant them as needed.
On Mon, 2002-08-26 at 22:27, Bruce Momj
On Wed, 2002-08-21 at 13:50, Marc G. Fournier wrote:
> On Wed, 21 Aug 2002, Bruce Momjian wrote:
>
> >
> > We learned a few lessons from previous releases. First, don't delay
> > the beta by days/weeks that drag on. Delay one month at a time.
> > Second, don't decide on a further delay the day
As you probably know, PostgreSQL is quickly approaching the beta period
for its next release (7.3).
It would be heavily appreciated if you could attack the new source base
starting now and throughout the beta period in an attempt to make the
next release extra secure and stable from the outset.
On Wed, 2002-08-21 at 13:13, Bruce Momjian wrote:
> Justin Clift wrote:
> > Bruce Momjian wrote:
> > >
> > > Justin Clift wrote:
> > > > Only two things which have the potential to be worth waiting for, from
> > > > what I'm aware of. There may be others:
> > > >
> > > > - Find out from Sir Mor
On Tue, 2002-08-20 at 16:46, Zeugswetter Andreas SB SD wrote:
> > >>> Hard to say what is good for those names imho, don't like
> > >>> "anytype" :-(
> > >>
> > >> How about "any"? It's a reserved word per SQL99, I think.
> >
> > > I would actually stick to opaque in that case, already used in
> anyarraytype-- for array_eq, array_dims
Will this allow generic array iterator functions in the future?
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tue, 2002-08-20 at 08:22, D'Arcy J.M. Cain wrote:
> On August 19, 2002 11:58 pm, Rod Taylor wrote:
> > On Mon, 2002-08-19 at 23:50, Christopher Kings-Lynne wrote:
> > The simple fix is to drop the money type entirely as it serves few
> > purposes -- but there are so
Looks like the expected files weren't updated.
Probably my fault, but the tests themselves are fine.
On Tue, 2002-08-20 at 01:37, Neil Conway wrote:
> The 'type_sanity' and 'domain' regression tests seem to fail with CVS
> HEAD. Here's the diff:
>
> *** ./expected/type_sanity.outSun Aug
On Mon, 2002-08-19 at 23:50, Christopher Kings-Lynne wrote:
> > > I'd like to see something done about this fairly soon, but it's not
> > > happening for 7.3 ...
> >
> > Hang on, you seem to be suggesting we release a major new upgrade, with
> > major new functionality, knowing it contains a way t
On Mon, 2002-08-19 at 13:14, Florian Weimer wrote:
> Justin Clift <[EMAIL PROTECTED]> writes:
>
> > You guys *definitely* write scarey code.
>
> Yes, indeed. My code has a lot of unnecessary and error-prone input
> validation checks because I don't trust the PostgreSQL parser.
Bah.. Check the
# Disallow TRUNCATE on tables that are involved in referential
constraints
The above is on the TODO list. Are there any thoughts as to what we
want to do with this? The patch I submitted earlier received heavy
feedback saying it wasn't wanted due to rules and triggers (foreign
keys) being diffi
> > In MSSQL this
> > is gotten around by allowing the properties of the data type to be
> > altered, e.g. in MSSQL you can turn the IDENTITY property on or off
>
> Rather pointless if it can be turned off, wouldn't you say?
>
> What I would do if I wanted such a guarantee is to make insertion
On Sun, 2002-08-18 at 02:35, Joe Conway wrote:
> Tom Lane wrote:
> > Joe Conway <[EMAIL PROTECTED]> writes:
> >>I agree 100%. If you want an index, unique constraint, or primary key on
> >>a SERIAL, I think you should explicitly add it. SERIAL should give me a
> >>column that automatically incre
27;t fix it.
> -------
>
> Rod Taylor wrote:
> > On Sat, 2002-08-17 at 22:08, Tom Lane wrote:
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > > I am not seeing the failure here on BSD/OS. I just fixed the
> > > > libpq-int.h problem.
On Sat, 2002-08-17 at 22:08, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I am not seeing the failure here on BSD/OS. I just fixed the
> > libpq-int.h problem. Please update to cvs current and let me know what
> > you see.
>
> FWIW, libpq seems to build fine here (HPUX 10.20)
n file included from fe-connect.c:24:
libpq-int.h:337: warning: `struct timeval' declared inside parameter
list
libpq-int.h:337: warning: its scope is only this definition or
declaration, which is probably not what you want.
fe-connect.c: In function `connectDBComplete':
fe-connect.c:1060: storage
I'd like to propose dropping the auto-creation of UNIQUE indexes on
serial columns for the following reasons:
1. Serials with indexes are quite difficult to handle in pg_dump. It
means that the implicitly created unique index must be destroyed prior
to loading the data, then re-created afterward
Is it possible for the cvs emails to include a URL to the appropriate
entries in cvs web?
The below is current:
Modified files:
src/backend/utils/adt: ruleutils.c
Is this possible?
Modified files:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/adt/ruleutils.c
> I have seen some negative reactions to the feature. I am willing to ask
> for a vote, if that is what people want. If not, I will apply the patch
> in the next day or two.
Please apply.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postm
> > Yes, after updating docs to the newer DTD I intend to make them XML
> > compliant to ensure they work with v5 of docbook in the future.
>
> Ah, an XML vs. SGML debate. I look forward to it.
This one is pretty simple. It's been announced that the docbook group
isn't looking to continue wit
> But how many people would even use it? I can't see adding the bloat
> unnecessarily and risking it accidently being turned on. Am I wrong
> and really alot of people actually want/need this?
At an absolute minimum there are two. Myself and Marc.
That said, this is a semi-required step to o
On Thu, 2002-08-15 at 00:01, Christopher Kings-Lynne wrote:
> > > Dependency - have pg_dump auto-create dependencies when
> > loading 7.2.X
> > > data?
> > >
> > > Are we as far as we can go here?
> >
> > The only trouble maker is foreign keys. If there was a nice way of
> > finding foreign k
> Dependency - have pg_dump auto-create dependencies when loading 7.2.X
> data?
>
> Are we as far as we can go here?
The only trouble maker is foreign keys. If there was a nice way of
finding foreign keys in 7.2 and prior it probably would have been
implemented a long time ago in p
Anyone mind if we bump the DTD version to Docbook 4.2?
This consists on all users who wish to build docs on installing the 4.2
DTD set, and updating some depreciated tags within the sgml files.
comment -> remark
docinfo -> appendixinfo, chapterinfo, bookinfo, etc.
What it buys is a number of u
On Wed, 2002-08-14 at 18:20, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > > I will vote against this as being a major loss of legibility. Perhaps
> > > we could compromise on controlling it by a GUC variable, though.
> >
> > I was afraid of that, but to pick up the theme of the day, I'm no
On Wed, 2002-08-14 at 16:32, Neil Conway wrote:
> A couple questions regarding encrypted passwords:
>
> (1) There was talk of changing the default value of the
> 'password_encryption' GUC variable for 7.3; AFAIK, this hasn't
> happened yet. Should this be done?
Since ODBC is capable of u
On Wed, 2002-08-14 at 14:34, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Oh, so try it with and without. I can do that, but it seems more of a
> > security problem where you were trying two names instead of one. Do
> > people like that?
>
> The nice thing about it is you can
> * Is anyone working on using standard foreign key creation commands
> instead of CREATE CONSTRAINT TRIGGER?
Submitted with the pg_constraint patch, and more recently updated to
match cvs tip. I believe Tom wishes to review this prior to
application.
---(end of broad
I believe the dictionary meaning of 'object' in this context would be 'a
cause for concern or attention'. Each of Peters uses of the word is
highly appropriate, as he was concerned and I'd agree with the
sentiments that those concepts needed attention.
Anyway, object with stars and strongly obje
On Wed, 2002-08-14 at 11:17, Ross J. Reedstrom wrote:
> On Wed, Aug 14, 2002 at 09:39:06AM -0500, Greg Copeland wrote:
> > On Tue, 2002-08-13 at 23:43, Curt Sampson wrote:
> > > Just my opinion of course, but I think it would be best to have a
> > > detailed description of how everything in inheri
I'm going to vote for either @ or %.
On Wed, 2002-08-14 at 00:11, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have no personal preference between period and @ or whatever. See if
> > you can get some other votes for @ because most left @ when the ORDER BY
> > idea came up f
greSQL unapplied patches list at:
>
> http://candle.pha.pa.us/cgi-bin/pgpatches
>
> I will try to apply it within the next 48 hours.
>
> -----------
>
>
> Rod Taylor wrote:
> > Appears there
> Tradeoffs, again ... What about emitting warnings after table drop
> (easy)/creation (not so easy !) ?
The warnings are certainly there now. Dependency code won't let you do
such a thing without specifying CASCADE.
Hopefully CREATE OR REPLACE VIEW will be applied soon, which solves part
two
> > that TODO item was written before we had dependencies, and I think
> > it's obsolete. Basically the point of the TODO was to avoid
> > having broken views --- and we have solved that problem.
>
> We may have broken views again when "alter table drop column" gets done
Any view depending on a
On Tue, 2002-08-13 at 12:22, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I was playing with this a while back (when I had initially added CASCADE
> > to tables). I believe that in the event of a crash the temp tables are
> > not removed until their
On Tue, 2002-08-13 at 11:18, Bruce Momjian wrote:
> Tom Lane wrote:
> > Gavin Sherry <[EMAIL PROTECTED]> writes:
> > > I'm thinking that temporary views should be pretty trivial to
> > > implement.
> >
> > ... except not so trivial, per the rest of your note.
> >
> > Do we actually need any such
On Tue, 2002-08-13 at 11:11, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > I'm thinking that temporary views should be pretty trivial to
> > implement.
>
> ... except not so trivial, per the rest of your note.
>
> Do we actually need any such feature? Views on temp tables alrea
> But I really seriously feel that this feature is a bad idea as presently
> implemented. If necessary, I'll volunteer to change it the way I think
> it should be (viz, initdb can set up a symlink to a specified xlog
> directory; no change from previous behavior anywhere else).
Neither solution
On Tue, 2002-08-13 at 07:49, Oleg Bartunov wrote:
> We have a patch for pg_dump which adds a possibility to dump
> a part of table, for example:
>
> dump Top.Science.Astronomy heirarchy from dmoz catalog
>
> pg_dump -d -t dmoz -w "select * from dmoz where path <@ 'Top.Science.Astronomy'" dmoz
>
On Tue, 2002-08-13 at 02:47, Jeroen T. Vermeulen wrote:
> On Mon, Aug 12, 2002 at 09:38:00PM -0300, Marc G. Fournier wrote:
> >
> > should be fixed ... looks like just an ownership issue on a new directory
>
>
> More like I uploaded that directory just as you were rsync'ing to
> anonymous CVS a
All of that said, the cost of the check is so small it may save someones
ass some day when they have a corrupted catalog and the below
assumptions are no longer true.
On Mon, 2002-08-12 at 18:40, Greg Copeland wrote:
> On Sun, 2002-08-11 at 21:15, Christopher Kings-Lynne wrote:
> > > Not a proble
> Maybe if some index had the indisclustered bit set one could select
> that; but is it possible for some table to have more than one index with
> it? Intuition (but no code observation) says no. And what happens with
> those tables that do not have any such index?
The bool marker sounds useful
In 7.2.1, the psql argument to import a file from a connected database
is \i. From the command line its -f.
Any chance we could make these consistent with eachother.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://ww
Just go with tradition and label all of your variables with a
v_. Never use columns or tablenames prefixed with a v_.
It's a quick way for determining what is what. Forcing use of a prefix
in some places and not others would not be a nice thing -- especially as
the core takes on more and more
Appears there is a problem finding the opclass when indexing a domain.
CREATE DOMAIN newint as int4;
CREATE TABLE tab (col newint unique);
ERROR: data type newint has no default operator class for access method
"btree"
You must specify an operator class for the index or define a
> > (/projects/cvsroot/interfaces/libpqxx/debian/#cvs.lock): Permission
> > denied
> > cvs server: failed to obtain dir lock in repository
> > `/projects/cvsroot/interfaces/libpqxx/debian'
> > cvs [server aborted]: read lock failed - giving up
>
> I only just added that directory, so chances are
P src/interfaces/libpqxx/configure.ac
cvs server: Updating src/interfaces/libpqxx/config
U src/interfaces/libpqxx/config/.cvsignore
cvs server: Updating src/interfaces/libpqxx/debian
cvs server: failed to create lock directory for
`/projects/cvsroot/interfaces/libpqxx/debian'
(/projects/cvsroot/in
I intend to make 'serial' and 'serial8' domains of the int4 and int8
datatypes. Now they're regular types and columns in \d will be marked
as such. This leaves analyze.c to create the defaults but no longer
will it be doing any datatype conversions.
pg_dump and psql will be taught to ignore the
> > Is it likely to have more than one function using a complex type like
> > that? If not, then allowing it's creation (not enforcing) could be
> > useful.
>
> That's what I was thinking. In cases where you want to use the type for
> several functions, use CREATE TYPE. If you only need the ty
I think it buys the same as SERIAL does for sequences.
Is it likely to have more than one function using a complex type like
that? If not, then allowing it's creation (not enforcing) could be
useful.
On Fri, 2002-08-09 at 19:03, Joe Conway wrote:
> Peter Eisentraut wrote:
> > Joe Conway writes
http://developer.postgresql.org/docs/postgres/buildlog.html
It would appear that the files point to the old urls, not the new ones
as per the cvs segregation.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister c
> An even more radical approach is to get rid of the hardwired index name
> lists in indexing.h, and instead expect CatalogOpenIndices to make use
> of the index OID lists that are maintained by the relcache (since 7.1 or
> so). Then the typical call would reduce to
>
> CatalogUpdateIndexes(
On Fri, 2002-08-02 at 13:53, Jeff Davis wrote:
> > Well, if you also have soundcard_products, in your example you could have a
> > product which is both a networkcard AND a soundcard. No way to restrict
> > that a product can be only one 'subclass' at a time... If you can make that
> > restriction
On Thu, 2002-08-01 at 00:42, Stephen Deasey wrote:
> Neil Conway said:
> >> FUNC_MAX_ARGS - disk/performance penalty for increase, 24, 32?
> >
> >Until someone takes the time to determine what the performance
> >implications of this change will be, I don't think we should
> >change this. Given tha
Perhaps I'm not remembering correctly, but don't SQL functions still
have an abnormally high cost of execution compared to plpgsql?
Want to try the same thing with a plpgsql function?
On Thu, 2002-08-01 at 18:23, Neil Conway wrote:
> Ok, here are some crude benchmarks to attempt to measure th
On Thu, 2002-08-01 at 15:33, Vince Vielhaber wrote:
> On Thu, 1 Aug 2002, Tom Lane wrote:
>
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > ... is once more 'normal' ...
> >
> > Uh, it's completely broken as far as I can tell.
> >
> > $ pwd
> > /home/postgres/pgsql/src/bin/pg_dump
> > $
On Thu, 2002-08-01 at 10:44, Neil Conway wrote:
> On Thu, Aug 01, 2002 at 12:01:52PM +0200, Karel Zak wrote:
> > Is there some common convention of names?
> functions. However, establishing a naming convention without
> breaking backwards compatibility might be tricky.
Supporting both names for
> Another idea is to change pg_hba.conf to not default to 'trust' but then
> the installing user is going to have to choose a password.
I like this approach. Set it to password (or md5) on local, and force
the request of a password during initdb.
If for some reason they forget their password, t
> As an implementor I'm always wary of using features nobody else has,
> especially in databases. So, if I'd want postgres to have one thing
> nobody else has, it would be the most complete standard SQL
> implementation - so it would at least be the other products' fault if
> I'd have to do any sp
The current ODBC drivers on the website don't appear to work with recent
development.
I'm able to login, but immediately after it throws the error 'Blank'
with a large negative number above (-2^16 or so).
I don't have Visual C, so would it be possible for someone to build a
new (working) driver
> > -Original Message-
> > From: Rod Taylor [mailto:[EMAIL PROTECTED]]
> > Sent: 29 July 2002 14:39
> > To: PostgreSQL-development
> > Subject: [HACKERS] GPL License
> >
> >
> > Given the GPL isn't wanted in the contrib directory, it
Given the GPL isn't wanted in the contrib directory, it may be wise to
take care of src/interfaces/odbc/license.txt
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Try this:
SELECT count(*)
FROM (
SELECT count(*)
FROM test
GROUP BY date_trunc('day', test_date)
) as qry;
On Fri, 2002-07-26 at 16:03, Yuva Chandolu wrote:
> Hi,
>
> We have a query "select count(count(*)) from test group by
> trunc(test_date)". This works fi
On Fri, 2002-07-26 at 12:55, Marc G. Fournier wrote:
> On Fri, 26 Jul 2002, Tom Lane wrote:
>
> > Rod Taylor <[EMAIL PROTECTED]> writes:
> > > This still doesn't allow john on db1 to be a different user than john on
> > > db2. To accomplish that (e
On Wed, 2002-07-24 at 02:22, Marc Lavergne wrote:
> I have a need for relation synonyms in PostgreSQL. I don't see it in
> 7.2.1 but the catalog seems to be able to support it more or less.
>
> Here's what I intend to do:
>
> 1) Create a duplicate record in pg_class for the base table informati
701 - 800 of 994 matches
Mail list logo
