On Sun, Jun 09, 2002 at 02:32:22AM -0300, Marc G. Fournier wrote:
> Right now, Sept 1st is the "preferred date to go beta" ... when Sept 1st
I agree with Bruce, Sept 1st is the deadline and right time for all
discussion about shift of this date is Sept 2nd. Not now, else you
never will see en
Le Samedi 8 Juin 2002 01:43, Scott Shattuck a écrit :
> What is the planned status of Java support in the engine? Is there anyone
> working on JVM integration at this stage and if not, how could we best
> integrate with the team to take on this task?
You may be interested in looking at PLjava on
On Fri, Jun 07, 2002 at 06:48:31PM -0700, Thomas Lockhart wrote:
>
> > Proposal #4: Create to_char(INTERVAL, 'format string') Function.
> > Reason: self-evident, I think.
>
> Oh. Didn't know it wasn't already there.
I'm _sure_ that to_char() is there for interval.
testt=# select to_char('33
On Mon, 2002-06-10 at 09:58, Karel Zak wrote:
> On Fri, Jun 07, 2002 at 06:48:31PM -0700, Thomas Lockhart wrote:
> >
> > > Proposal #4: Create to_char(INTERVAL, 'format string') Function.
> > > Reason: self-evident, I think.
> >
> > Oh. Didn't know it wasn't already there.
>
> I'm _sure_ tha
> > I'm _sure_ that to_char() is there for interval.
> >
> > testt=# select to_char('33s 15h 10m 5month'::interval, 'HH:MI:SS Month');
> > to_char
> >
> > 03:10:33 May
> > (1 row)
>
> Does "May" make sense for an _interval _ ? (Feb 22 + May = Jul 22)?
>
> Wo
I've looked in fmgr.h and there is no definition of this type there - it
uses the type, but does not define it.
Peter Eisentraut wrote:
>
> Tony Griffiths writes:
>
> > I've done a search of all the header files in my installation (and also
> > all the source files that I compiled), and cannot
How about a SOAP interface and a web-based front end that provides the cross
platform support? My company's TIBET framework would provide a solid
foundation for this kind of admin suite. In fact, we're already in the
planning stages on doing just that.
ss
Scott Shattuck
Technical Pursuit Inc.
SuSE Linux 8.0
On Fri, 2002-06-07 at 07:41, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Since we now have an official entry in /etc/services, shouldn't we be able
> > to make use of it, by using getservbyname() if a nonnumeric port number is
> > specified?
>
> Is any OS actually shipping
> Is any OS actually shipping us in /etc/services?
It's right here in SuSE Linux 8.0. It was not in 7.3, so maybe it's
officially included from now on.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Sun, 9 Jun 2002, Tom Lane wrote:
>Can't you set up a situation where the failure is reproducible, then?
>On a day where you get the failure, dump the database and see if
>you can load the data into a fresh database and reproduce the problem.
>
Ok, I will do that...
>I don't necessaril
I've found the mistake - as usual it's down to me! I didn't realise that
I had to include postgres.h before including geo_decls.h All now compiles
ok.
Tony
Tony Griffiths wrote:
[EMAIL PROTECTED]">
I've looked in fmgr.h and there is no definition of this type there - ituses the type, but do
On Mon, 2002-06-10 at 10:49, Karel Zak wrote:
>
> > > I'm _sure_ that to_char() is there for interval.
> > >
> > > testt=# select to_char('33s 15h 10m 5month'::interval, 'HH:MI:SS Month');
> > > to_char
> > >
> > > 03:10:33 May
> > > (1 row)
> >
> > Does "May
NunoACHenriques <[EMAIL PROTECTED]> writes:
> Neither I believe it because the machine is well tested (including a
> 24h memtest). But there is something I can't get of my mind: once a day my
> app "forces" PG to "play" with some 3GB of disk data in a ext2 fs. It is
> known that sometimes ex
On Mon, Jun 10, 2002 at 04:26:47PM +0200, Hannu Krosing wrote:
> > to_char() convert interval to 'tm' and make output like this struct,
>
> My point is that to_char-ing intervals by converting them to dates is
> non-intuitive.
>
> It is really confusing to say that an interval of 5 months = "
In a 7.3 dev test database, I have a table called msysconf in a schema
called biblio. If I execute:
ALTER TABLE biblio.msysconf OWNER TO dpage
I get:
ERROR: msysconf_idx is an index relation
There is an index with this name on the table.
Any ideas?
Regards, Dave.
--
Scott,
I just started a java admin tool project on sf called
www.sf.net/projects/jpgadmin, which should be able to handle web based
interfaces, the idea being to seperate the model and view so that we can
support a swing or web interface.
Dave
On Fri, 2002-06-07 at 18:05, Scott Shattuck wrote:
Tony Griffiths <[EMAIL PROTECTED]> writes:
> I've looked in fmgr.h and there is no definition of this type there - it
> uses the type, but does not define it.
Eh?
typedef Datum (*PGFunction) (FunctionCallInfo fcinfo);
Looks like a definition to me ...
regards, t
Christoph Haller <[EMAIL PROTECTED]> writes:
> Based on an entry in the mailing list from 30 Oct 2001
> about efficient deletes on subqueries,
> I've found two ways to do so (PostgreSQL 7.2.1):
> ...
> Is there a way to put the second form (more complicated, but faster)
> in one statement?
>
On Mon, 2002-06-10 at 15:43, Karel Zak wrote:
> On Mon, Jun 10, 2002 at 04:26:47PM +0200, Hannu Krosing wrote:
>
> > > to_char() convert interval to 'tm' and make output like this struct,
> >
> > My point is that to_char-ing intervals by converting them to dates is
> > non-intuitive.
> >
> >
On Mon, 2002-06-10 at 15:56, Tom Lane wrote:
> Christoph Haller <[EMAIL PROTECTED]> writes:
> > Based on an entry in the mailing list from 30 Oct 2001
> > about efficient deletes on subqueries,
> > I've found two ways to do so (PostgreSQL 7.2.1):
> > ...
> > Is there a way to put the second for
Tom Lane wrote:
> Christoph Haller <[EMAIL PROTECTED]> writes:
>
> DELETE FROM relation_expr [ FROM table_ref [ , ... ] ]
> [ WHERE bool_expr ]
>
> The two FROMs in the second form look a little weird, but they help to
> make a clear separation between the deletion target table and t
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > I *really* wish ppl would stop harping on the length of the last beta
> > cycle ... I will always rather delay a release due to an *known*
> > outstanding bug, especially one that just needs a little bit more time to
> > work out
Hi ,
I am extremely new to PostGreSql. If any one can please answer
this question of mine. I want to insert/update records into the
postgres database through C or perl code. The only condition is
that it should be efficient. Can anybody tell me the difference
between ecpg and libpq and which
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Agreed on all accounts ... which is why this time, I want to do a proper
> > branch when beta starts ... hell, from what I've seen suggested here so
> > far, we have no choice ... At least then we can 'rip out' something from
> >
> -Original Message-
> From: vikas p verma [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 10, 2002 1:10 PM
> To: [EMAIL PROTECTED]
> Subject: [HACKERS] PostGres Doubt
>
>
> Hi ,
>
> I am extremely new to PostGreSql. If any one can please answer
> this question of mine. I want to inser
Hi,
We are moving to Postgres from Oracle. We have a few tables that have around
8 to 10 millions of rows and their size increases very rapidly(deletions are
very less on these tables). How will Postgres hanlde very big tables like
this? or would it be very slow when compared to Oracle? Do you ha
Karel, Hannu,
To be perfectly honest, I was looking at my 7.1 documentation (courtesy
of DOSSIER) and hadn't realized that 7.2's implementation had got as
far as a function. I had tried to_char(interval) on 7.2.1, received
what looked like gibberish in return, and assumed that it was
unimplement
Hannu Krosing wrote:
> What about
>
> DELETE relation_expr FROM relation_expr [ , table_ref [ , ... ] ]
> [ WHERE bool_expr ]
>
> or
>
> DELETE relation_expr.* FROM relation_expr [ , table_ref [ , ... ] ]
> [ WHERE bool_expr ]
So make the initial FROM optional and allow the later F
On Mon, 10 Jun 2002, Bruce Momjian wrote:
> Tom Lane wrote:
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > Agreed on all accounts ... which is why this time, I want to do a proper
> > > branch when beta starts ... hell, from what I've seen suggested here so
> > > far, we have no choice
Marc G. Fournier wrote:
> On Mon, 10 Jun 2002, Bruce Momjian wrote:
>
> > Tom Lane wrote:
> > > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > > Agreed on all accounts ... which is why this time, I want to do a proper
> > > > branch when beta starts ... hell, from what I've seen suggested h
On Monday 10 June 2002 02:46 pm, Marc G. Fournier wrote:
> Based on everything I've heard/seen in this thread, we seem to be looking
> at:
> 1. Branch on Sept 1st, regardless of almost anything
> 2. Once Branch created, any *partially implemented* features will get
>rip'd out of the -STABLE
On Mon, 10 Jun 2002 09:56:27 -0400, Tom Lane <[EMAIL PROTECTED]>
wrote:
>Does anyone know whether other systems that support the UPDATE extension
>for multiple tables also support a DELETE extension for multiple tables?
>If so, what's their syntax?
MSSQL seems to guess what the user wants. All t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Hannu Krosing wrote:
>> What about
>>
>> DELETE relation_expr FROM relation_expr [ , table_ref [ , ... ] ]
>> [ WHERE bool_expr ]
>>
>> or
>>
>> DELETE relation_expr.* FROM relation_expr [ , table_ref [ , ... ] ]
>> [ WHERE bool_expr ]
> So make the
Lamar Owen <[EMAIL PROTECTED]> writes:
> Historically we've concentrated our development efforts during beta to
> 'fixing beta problems only' -- but that model produces these
> extraordinarily long cycles, IMHO. In the meantime people are
> literally chomping at the bit to do a new feature -- to
Manfred Koizar <[EMAIL PROTECTED]> writes:
>> If so, what's their syntax?
> MSSQL seems to guess what the user wants.
Gack. Nothing like treating mindless syntax variations as a "feature"
list...
> All the following statements do the same:
> (1) DELETE t1 FROM t2 WHERE t1.i=t2.i
> (2a) DELET
Tom,
> Probably we should have temp table creation allowed to all by default.
> I'm not convinced that that's a good idea for schema-creation privilege
> though. Related issues: what should initdb set as the permissions for
> template1? Would it make sense for newly created databases to copy
>
Tom,
> >> If so, what's their syntax?
>
> > MSSQL seems to guess what the user wants.
>
> Gack. Nothing like treating mindless syntax variations as a "feature"
> list...
I vote that we stick to a strick SQL92 interpretation, here.
1) It's standard
2) Strict syntax on DELETE statements is
Yuva,
> Also anyone know of any perticular documentation/links that talks
> specifically about "migrating to Postgres from Oracle"?, Please let me know
> if you have kind of document that would be of great use to us.
Please see Techdocs ( http://techdocs.postgresql.org/ ) for performance
white
> -Original Message-
> From: Josh Berkus [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 10, 2002 3:42 PM
> To: Tom Lane; Manfred Koizar
> Cc: Christoph Haller; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] [SQL] Efficient DELETE Strategies
>
> Tom,
>
> > >> If so, what
Is libpq/PQconnectdb() reentrant? I've tried repeatedly over time and
it seems to incur segfaults every single time.
-d
Dann Corbit wrote:
>The libpq functions are reentrant. These will be useful for just about
>any project.
>
>
---(end of broadcast)--
On Monday 10 June 2002 04:11 pm, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Historically we've concentrated our development efforts during beta to
> > 'fixing beta problems only'
> There is a downside to changing away from that approach.
There are downsides to every approach.
This
Hannu Krosing wrote:
> DELETE relation_expr FROM relation_expr [ , table_ref [ , ... ] ]
> [ WHERE bool_expr ]
This in some ways is similar to Oracle where the FROM is optional in a
DELETE (ie. DELETE foo WHERE ...). By omitting the first FROM, the
syntax ends up mirroring the UPD
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Hannu Krosing wrote:
> >> What about
> >>
> >> DELETE relation_expr FROM relation_expr [ , table_ref [ , ... ] ]
> >> [ WHERE bool_expr ]
> >>
> >> or
> >>
> >> DELETE relation_expr.* FROM relation_expr [ , table_ref [ , ... ] ]
>
OK I know this has been long delayed but I've finished some work on the
above. The coster is actually doing a fairly good job. I only recieved
one submission from someone with data that replicated the problem, and
was myself hard pressed to replicate the situation. It's more-or-less a
fence
> Given the plethora of mutually incompatible interpretations that MSSQL
> evidently supports, though, I fear we can't use it as precedent for
> making any choices :-(.
>
> Can anyone check out other systems?
MySQL:
6.4.6 DELETE Syntax
DELETE [LOW_PRIORITY | QUICK] FROM table_name
[WHERE
On Mon, 10 Jun 2002, Yuva Chandolu wrote:
> We are moving to Postgres from Oracle. We have a few tables that have around
> 8 to 10 millions of rows and their size increases very rapidly(deletions are
> very less on these tables). How will Postgres hanlde very big tables like
> this?
Uh..."what b
46 matches
Mail list logo
