On Fri, Oct 08, 2004 at 08:40:56PM +0200, Michael Paesold wrote:
> I hope you will be willing to comment on the issues when times come. I am
> not really satisfied myself, but without further discussion I did not want
> to continue to work on it. Anyway, I understand this is not the right time
On Tue, Aug 17, 2004 at 03:33:01PM -0300, Haroldo Stenger wrote:
Haroldo,
> On Wed, 11 Aug 2004 11:47:35 -0400, Tom Lane <[EMAIL PROTECTED]> wrote:
> > The other objection is that this would create very substantial overhead.
>
> why?
Establishing a savepoint is a non-trivial operation (cost-wis
On Tue, Aug 10, 2004 at 12:24:06PM -0400, Tom Lane wrote:
> My discovery last night of a WAL synchronization error in pg_clog led me
> to take a look at pg_subtrans too. I soon realized that in fact we are
> not WAL-logging pg_subtrans updates at all: subtransaction start sets up
> a pg_subtrans e
On Mon, Aug 09, 2004 at 04:44:58PM +0800, Christopher Kings-Lynne wrote:
> I read this in the release notes:
>
> ---
> # Database-wide ANALYZE does not hold locks across tables (Tom)
>
> This reduces the potential for deadlocks against other backends that
> want exclusive locks on tables. To get
On Mon, Aug 09, 2004 at 11:56:17AM +1000, fastpgs wrote:
> On Sun, 8 Aug 2004 08:19, Alvaro Herrera wrote:
>
> > If the change is global, what should happen on other sessions that have
> > a deferred event from that trigger concurrently with the one that
> > modifies it? Should the answer be diff
On Wed, Jul 28, 2004 at 08:19:17PM -0400, Tom Lane wrote:
Very cool and interesting idea.
> Does anyone have a problem with this macro syntax? The try/catch names
> are stolen from Java, so I'm figuring they won't terribly surprise any
> modern programmer, but I'm open to different names if anyo
On Tue, May 18, 2004 at 12:39:08PM -0400, Neil Conway wrote:
> A copy that claims to "represent an almost indistinuishable delta on the
> actual SQL 2003 database standard" is available online here:
>
> http://www.wiscorp.com/sql/sql_2003_standard.zip
Those are PDFs AFAIR, not easily greppable
On Mon, May 17, 2004 at 04:55:50PM +0200, Zeugswetter Andreas SB SD wrote:
>
> > It is too late to think about pushing back another month. We had this
> > discussion already. June 1 is it.
>
> I thought the outcome of that discussion was June 15 ?
I think there was no outcome. There was no of
On Fri, Apr 23, 2004 at 08:38:29PM -0400, Alvaro Herrera Munoz wrote:
> On Fri, Apr 23, 2004 at 07:00:05PM -0400, Bruce Momjian wrote:
> >
> > Please recompile with debug symbols and report back the stack trace.
> > See the faq on running debug.
>
> No, I already
On Fri, Apr 23, 2004 at 07:00:05PM -0400, Bruce Momjian wrote:
>
> Please recompile with debug symbols and report back the stack trace.
> See the faq on running debug.
No, I already did that (all my builds are like that anyway and I read
stack traces more frequently than I'd like). The "can't r
On Fri, Dec 12, 2003 at 10:13:56AM -0800, David Fetter wrote:
> I'm looking to the SQL WITH clause as a way to get better regex
> support in PostgreSQL. I've been chatting a little bit about this,
> and here's an idea for a behavior. Implementation details TBD.
I think you could be rather looki
On Thu, Dec 11, 2003 at 06:03:05PM -0400, Peter Eisentraut - PostgreSQL wrote:
> Modified files:
> src/bin/initdb : nls.mk
> Added files:
> src/bin/initdb/po: it.po
Are you going to keep managing these things? I received your email about a
CVS write account so I could handle them f
On Thu, Dec 11, 2003 at 04:14:43PM +0100, Manfred Koizar wrote:
> On Sat, 6 Dec 2003 10:43:18 -0500 (EST), Bruce Momjian
> <[EMAIL PROTECTED]> wrote:
> >Where are we on nested transactions. Is it something we can get for 7.5?
>
> I honestly don't know. I've been working on other things lately an
On Fri, Nov 21, 2003 at 04:24:25PM -0500, Matthew T. O'Connor wrote:
> I don't want to add tables to existing databases, as I consider that
> clutter and I never like using tools that clutter my production
> databases. [...]
>
> Actually, this might be a necessary addition as pg_autovacuum cur
On Thu, Nov 20, 2003 at 10:39:24AM -0500, Tom Lane wrote:
> > (c) Do I need to consider inheritance?
>
> Yes. I think it'd be good if things were constrained so that columns
> 1..n in a parent table always matched columns 1..n in every child,
> which is not true now after adding/dropping colum
On Tue, Oct 28, 2003 at 04:48:59PM -0500, Tom Lane wrote:
> 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 compl
On Tue, Oct 14, 2003 at 07:52:55PM +, Jon Jensen wrote:
> Is there a mailing list somewhere that all the CVS commits get sent to?
Yes, pgsql-committers.
> Other projects I've worked on have such a list, and each commit message is
> followed by a complete diff (usually with -u for readabili
On Thu, Oct 02, 2003 at 10:09:12PM +0300, Hannu Krosing wrote:
> So what you really need is the CLUSTER command to leave pages half-empty
> and the tuple placement logic on inserts/updates to place new tuples
> near the place where they would be placed by CLUSTER. I.e. the code that
> does actual
On Mon, Sep 15, 2003 at 04:36:10PM -0400, tachuelita wrote:
> I was following an example on a book, and when I compiled it, it
> finishes with the error: 1075 Function Prototypes are an ANSI feature.
Huh, you need the real compiler from HP. The one bundled with the
operating system is apparently
On Tue, Sep 09, 2003 at 04:53:06PM +0200, Gaetano Mendola wrote:
> "Andrew Dunstan" <[EMAIL PROTECTED]> wrote:
> > The particular assertion that was proposed doesn't strike me as terribly
> > useful - It should be checked at the point of call rather than inside
> > pstrdup, I should have thought.
On Thu, Sep 04, 2003 at 11:21:05AM -0700, Jenny - wrote:
> >I think the locks would actually by represented by PROCLOCK structures.
> >The LOCK structures are for lockable objects, not for actual locks.
>
> Well,from what i understand, PROCLOCK stores the TransactionID and the LOCK
> its holding
On Thu, Sep 04, 2003 at 08:56:31AM -0700, Jenny - wrote:
> I am working on a project that involves displaying locking information
> about each lock taken, whether it be a row level or table leve llock.
> When dealing with struct LOCK (src/include/storage) i have noticed that
> postgreSQL creates
On Wed, Sep 03, 2003 at 01:28:16PM +0800, Christopher Kings-Lynne wrote:
> Hi guys,
>
> Where can I find a list of all the 'special' characters in the ~* operator?
They are the same for the ~ operator, and should be listed at the reference page
for regular expressions...
http://developer.postgre
On Tue, Aug 12, 2003 at 04:01:33PM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Can I have a TODO for this?
>
> * Prevent accidental re-use of sysids for dropped users and groups
>
> The other part of the thread was something like
>
> * Prevent dropping user that still
On Tue, Aug 12, 2003 at 03:36:07PM -0400, Tom Lane wrote:
> This leaves us with a bit of a problem, though, because there isn't any
> libpq API that allows access to this speedup. I put in a routine to
> support Parse/Bind/Execute so that people could use out-of-line
> parameters for safety reaso
Hackers,
Two buglets:
The first one is in createlang, trying to create a language without
enough permission:
$ createlang -d alvherre plpgsql
createlang: language installation failed: ERROR: c: permission denied
What's the "c" it's complaning about?
The second one is in pg_get_triggerdef():
On Wed, Jul 30, 2003 at 10:33:55PM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom, you saw this suggestion, right?
>
> I didn't hear anyone else agreeing with it ...
Well, if this needs a vote, I'm for something like maximum/default/minimum
rather than the way it curre
Hackers,
Is there a way to create a table from a prepared statement? CREATE TABLE AS
explicitly says you have to use a SELECT statement, and the SELECT INTO
syntax doesn't seem to allow the use of a prepared statement either. I
don't see a way to use the prepared statement as a function nor as a
On Thu, Jun 05, 2003 at 09:44:21AM -0600, scott.marlowe wrote:
> On Thu, 5 Jun 2003, Nigel J. Andrews wrote:
> Everything Nigel just wrote plus one thing.
>
> If it comes down to it, we could always require a --locale setting and
> refuse to initdb without it. That way, whether it's in an RPM o
On Wed, May 28, 2003 at 12:59:56PM +0200, Sailesh Krishnamurthy wrote:
> elog(NOTICE should send NOTICE messages to the psql client (I think !)
> while elog(LOG while only send it to the logfile you might have
> specified while starting the postmaster
Whether a given elog level is sent to the po
On Wed, May 28, 2003 at 09:04:18AM -0400, Michael Brusser wrote:
> > Well, first thing I'd ask is whether the other installation is using
> > the same locale settings.
> Oh, yes, I am very sure of that.
Note that while the machine reports the C locale, pg_controldata
actually said the database was
31 matches
Mail list logo
