Rod Taylor <[EMAIL PROTECTED]> writes:
> On Wed, 2004-10-20 at 14:07, Tom Lane wrote:
>> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
>>> troels=# create table lookat_feature(
>>> troels(# feature_id char(4),
>>> troels(# status varchar(2) default 'TODO'
> I think the bug is that default
At 05:41 AM 21/10/2004, Robert Treat wrote:
I've been thinking of an alternative solution that sounds very similar
to this. The idea is to output the CREATE TABLESPACE commands inside
pg_dump
...
1) tablespace already exists
to fail, but since we no longer stop on error during restore,
A fact
Tom Lane wrote:
I wrote:
Yeah. The intent of the protocol design was that the recipient could
skip over the correct number of bytes even if it didn't have room to
buffer them, but the memory allocation mechanism in the backend makes
it difficult to actually do that. Now that we have PG_TRY, thoug
On Wed, Oct 20, 2004 at 07:10:35PM +0200, Manfred Spraul wrote:
> [EMAIL PROTECTED] wrote a few months ago:
>
> >PostgreSQL's behavior on these cases is poor. I don't think anyone
> >who has tried to use PG for this sort of thing will disagree, and
> >yes it is getting better. Does anyone else c
On Tue, 2004-10-19 at 21:06, Philip Warner wrote:
> At 04:20 AM 20/10/2004, Tom Lane wrote:
> >Nope. I can break that trivially, eg:
>
> Thats why in my first message I mentioned escaping and unescaping all '%'
> in the deinition.
>
>
> >There's also the nontrivial matter of how pg_dump would
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
../../src/Makefile.shlib:327: warning: overriding commands for target `libtsearch2.a'
../../src/Makefile.shlib:262: warning: ignoring old commands for target `libtsearch2.a'
Broken coding in the WIN32 parts of Makefile.shlib? I do
On Wed, 2004-10-20 at 14:07, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > troels=# create table lookat_feature(
> > troels(# feature_id char(4),
> > troels(# status varchar(2) default 'TODO'
> The alternative would seem to be decreeing that this is not a bug.
>
> C
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> troels=# create table lookat_feature(
> troels(# feature_id char(4),
> troels(# status varchar(2) default 'TODO'
> troels(# );
> CREATE TABLE
> troels=# alter table lookat_feature
> troels-# alter column status type varchar(4);
> ALTER TABL
Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> dblink causeing PG to die with sig11
Works here, so you're going to have to do some digging of your own ...
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsu
The buildfarm has identified yet another failure under SPARC/Solaris 8 as
outlined in.
http://oicu.homedns.org:81/cgi/show_log.pl?nm=potorooo&dt=2004-10-20%2002:30:01
dblink causeing PG to die with sig11
--
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx: 250.763.1759
http:
[EMAIL PROTECTED] wrote a few months ago:
PostgreSQL's behavior on these cases is poor. I don't think anyone who has
tried to use PG for this sort of thing will disagree, and yes it is
getting better. Does anyone else consider this to be a problem? If so, I'm
open for suggestions on what can be don
On 10/15/2004 1:02 PM Nurlan M. Mukhanov could be overheard saying::
Hello!
I wrote this css file 2 years ago. It's very useful when using docs.
Can you add it in mainstream?
You might want to consider revising it to include fallbacks to standards
(or common aliases) such as Helvetica, Times, C
Hi,
I've read a few of the recent posts about 2-phase-commit support. I
noticed some discussion related to persisting the state of in-doubt
transactions, and thought you might be able to take advantage of work that
has been going on in the area of transaction logs.
I'm working on a project (h
> "Gavin" == Gavin Sherry <[EMAIL PROTECTED]> writes:
Gavin> I'm uncertain about the potential benefit of
Gavin> this. Isn't/shouldn't the effects of caching be assisting
Gavin> us here?
It all depends on how large your table is, and how busy the system is
(other pressures on the
D. Richard Hipp wrote:
Client/server database engines clearly have their place. But they
are not always the best solution to every data storage problem.
Nobody has suggested otherwise AFAICS. What we have suggested is that a
client/server system is a bad place to start when looking for an
e
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I suspect that no one on the planet
except Bruce and myself have ever actually run this script.
Then why don't we just remove it? Problem solved ...
Because it's a needed maintenance tool. There isn'
Clinging to sanity, [EMAIL PROTECTED] mumbled into her beard:
> I would like to know if there are any discussions about
> creating an embedded version on postgresql. My thoughts
> go towards building/porting a sqlite equivalent of pg.
People periodically "drive by" and suggest that PostgreSQL woul
Christopher Browne <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
>
> It also seems quite curious why in-process embedding should be so
> attractive;
>
People seem not to care whether or not the RDBMS runs in-process or
in a separately forked process. The attribute that conce
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I suspect that no one on the planet
>> except Bruce and myself have ever actually run this script.
> Then why don't we just remove it? Problem solved ...
Because it's a needed maintenance tool. There isn't any particularly
good reas
Tom Lane wrote:
I suspect that no one on the planet
except Bruce and myself have ever actually run this script.
Then why don't we just remove it? Problem solved ...
cheers
andrew
---(end of broadcast)---
TIP 7: don't forget to increase your free s
20 matches
Mail list logo
