Does anyone know how I should modify MergeAttributes to support dropped
columns?
If the parent column is dropped, should I perhaps just instead of going:
def = makeNode(ColumnDef);
I could go something like:
def = makeNullNode(); (or whatever the correct function is)
Or should I modify or re
I have faced a problem with encoding conversion while the database is
starting up. If postmaster accepts a connection request while in the
state, it issues a fatal message "The database system is starting
up". Then the encoding conversion system tries to convert the message
to client encoding if n
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > All backend functions would still use real attnum's. And I doubt that
> > backend will ever work though system views.
> > Adding them should touch _only_ CREATE TABLE, ADD COLUMN, DROP COLUMN
> > plus the system views and possibly output from SELECT(
I have committed many support files for CREATE CONVERSION. Default
conversion procs and conversions are added in initdb. Currently
supported conversions are:
UTF-8(UNICODE) <--> SQL_ASCII, ISO-8859-1 to 16, EUC_JP, EUC_KR,
EUC_CN, EUC_TW, SJIS, BIG5, GBK, GB18030, UHC,
> Should every elog() have an error code? I'm not sure -- there are many
> elog() calls that will never been seen by the user, since the error
> they represent will be caught before control reaches the elog (e.g.
> parse errors, internal consistency checks, multiple elog(ERROR)
> for the same user
[EMAIL PROTECTED] (Tony Reina) writes:
> db02=# explain select distinct area from center_out_cell where subject
> = 'M' and arm = 'R' and rep = 10 and success = 1 and direction = 1;
> NOTICE: QUERY PLAN:
> Unique (cost=87795.47..87795.80 rows=13 width=5)
> -> Sort (cost=87795.47..87795.47 r
Yes, our GiST supports variable-length keys.
Take a look on http://www.sai.msu.su/~megera/postgres/gist/
Oleg
On Wed, 17 Jul 2002, Eric Redmond wrote:
> Could anyone familiar with the pg version of GiST tell me if the
> framework allows entries in the tree as non-uniform sizes (in other
I'm using Postgres 7.2.1 on a dual-Athlon running RedHat 7.3bigmem
with 2 Gig of RAM and a 240 Gig RAID 5 (3ware IDE RAID). I just did a
'vacuum analyze' on the database, however the same query to two
similar tables is coming up quite different. The two tables only
differ in that one ("center_out_
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > > assemble all the files we need (as determined by configure) into a static
> > > library and link all executables with that. That way we don't have to
> > > deal with the individual files in each individual makefile.
> >
> > I like that a lot. B
J. R. Nield wrote:
> I will do something like this, but reserve 16 bytes for it just in case
> we change our minds. It needs to be different among systems on the same
> machine, so there needs to be a time value and a pseudo-random part as
> well. Also, 'hostname' will likely be the same on many m
One of my machines has two CPUs, and in some cases I build a pair
of indexes in parallel to take advantage of this. (I can't seem
to do an ALTER TABLE ADD PRIMARY KEY in parallel with an index
build, though.) Recently, though, I received the message "ERROR:
simple_heap_update: tuple concurrently
On Wed, 2002-07-17 at 01:25, Bruce Momjian wrote:
>
> We only patch configure.in. If you post to hackers, they can give you
> assistance and I will try to help however I can. I can so some
> configure.in stuff for you myself.
Thanks for the offer. The only thing I was changing it for was to te
I don't know how our marketing came up third most popular but I think the
order is, Oracle, MySQL, and PostgreSQL or maybe Oracle, MSSQL and
PostgreSQL. I'm sure there is some criterion by which PostgreSQL is tenth
and by some other its number one.
Of course, my posting was about Point In Time Re
On July 17, 2002 05:45 pm, Richard Tucker wrote:
> We also have implemented a roll forward recovery mechanism. We modified a
> 7.2.1 version of Postgres.
> ...
Excellent! I can't wait. When will it be in current?
> The BIG THING we have not done is address the issue that add/drop tables
> and
Neil Conway writes:
> I'd like to implement error codes. I think they would be pretty useful,
> although there are a few difficulties in the implementation I'd like
> to get some input on.
OK, allow me to pass on to you the accumulated wisdom on this topic. :-)
> Should every elog() have an err
Bruce Momjian writes:
> Can we move them to src/port rather than src/utils? Port makes more
> sense to me because that's what they are. Maybe is should be called
> src/libc?
Well, there is a bit of a history in picking a really silly name for this
library. GCC calls it libiberty, Kerberos cal
Tom Lane writes:
> > assemble all the files we need (as determined by configure) into a static
> > library and link all executables with that. That way we don't have to
> > deal with the individual files in each individual makefile.
>
> I like that a lot. But will it work for libpq?
No, just f
Rod Taylor wrote:
> > server powered by PostgreSQL, the third most popular database, and a
> >
> >^
>
> > Wonder why we are "the third most popular database". I think that's
> > good?
>
> You'll notice they didn't qualify where. On this list, it's probably
> #1.
> server powered by PostgreSQL, the third most popular database, and a
>
>^
> Wonder why we are "the third most popular database". I think that's
> good?
You'll notice they didn't qualify where. On this list, it's probably
#1. Within Progress software perhaps we'
Bruce Momjian wrote:
> Richard Tucker wrote:
> >
> > We also have implemented a roll forward recovery mechanism. We modified a
> > 7.2.1 version of Postgres.
> > The mechanism is designed to provide a means of recoverying from the loss or
> > corruption of media. It provides for duplicating wal_
Richard Tucker wrote:
>
> We also have implemented a roll forward recovery mechanism. We modified a
> 7.2.1 version of Postgres.
> The mechanism is designed to provide a means of recoverying from the loss or
> corruption of media. It provides for duplicating wal_files so that if a
> wal_file is
Neil, attached are three email messages dealing with error message
wording.
I like Tom's idea of coding only the messages that are common/user
errors and leaving the others with a catch-all code.
We now have more elog levels in 7.3, so it should be easier to classify
the messages.
I can see th
We also have implemented a roll forward recovery mechanism. We modified a
7.2.1 version of Postgres.
The mechanism is designed to provide a means of recoverying from the loss or
corruption of media. It provides for duplicating wal_files so that if a
wal_file is lost roll forward recovery can rec
On Wed, Jul 17, 2002 at 03:57:56PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] (Neil Conway) writes:
> > Should every elog() have an error code?
>
> I believe we decided that it'd be okay to use one or two codes defined
> like "internal error", "corrupted data", etc for all the elogs that are
> no
[EMAIL PROTECTED] (Neil Conway) writes:
> Should every elog() have an error code?
I believe we decided that it'd be okay to use one or two codes defined
like "internal error", "corrupted data", etc for all the elogs that are
not-supposed-to-happen conditions. What error codes are really for is
d
Could anyone familiar with the pg version of GiST tell me if the
framework allows entries in the tree as non-uniform sizes (in other
words, variable-length keys)? I want to write an extension for a
TV-tree, but this is an essential component.
Thanks;
Eric Redmond
---(end
Tom Lane writes:
> So the idea is to remove proimplicit again? We could still do that
> before 7.3, since no user depends on it yet. Are you intending a new
> system catalog to hold casts?
Yeah, it seems I forgot to mention that.
Btw., it occurred to me that this could also be the direction t
Neil Conway writes:
> My suggestion is: since fmtId() is almost always used with
> appendPQExpBuffer(), we should add a wrapper function to pg_dump
> that accepts an extra escape sequence (%S, or %i, perhaps), which
> would properly quote the input string before passing it to
> appendPQExpBuffer(
I'd like to implement error codes. I think they would be pretty useful,
although there are a few difficulties in the implementation I'd like
to get some input on.
Should every elog() have an error code? I'm not sure -- there are many
elog() calls that will never been seen by the user, since the e
"Luis Alberto Amigo Navarro" <[EMAIL PROTECTED]> writes:
> -> Seq Scan on part (cost=0.00..12399.00 rows=1 width=4) (actual
>time=24.88..4076.81 rows=10856 loops=1)
Seems like the major misestimation is above: the LIKE clause on part is
estimated to select just one row, but it selects 10856 o
The first thing to point out is that the estimated cost is measured in
terms of page reads while the actual time is measured in milliseconds. So
even if the cost estimate is accurate it is unlikely that those numbers
will be the same.
-N
--
Nathan C. Burnett
Research Assistant, Wisconsin Networ
On Wed, Jul 17, 2002 at 11:19:40PM +0800, Christopher Kings-Lynne wrote:
> > i spoke w/jan some time ago (in a hurry now -- have to call salvation army
> > to have them pick up my couch!).
> >
> > i need to jump in an discuss/get an assignment off the todo list. i am a cs
> > doctoral student at g
Hannu Krosing <[EMAIL PROTECTED]> writes:
> All backend functions would still use real attnum's. And I doubt that
> backend will ever work though system views.
> Adding them should touch _only_ CREATE TABLE, ADD COLUMN, DROP COLUMN
> plus the system views and possibly output from SELECT(*), if we
> i spoke w/jan some time ago (in a hurry now -- have to call salvation army
> to have them pick up my couch!).
>
> i need to jump in an discuss/get an assignment off the todo list. i am a cs
> doctoral student at gmu in va.
>
> i am the best programmer in the world.
Wow.
Chris
--
> > Has anyone committed something that would cause me to be getting doubles of
> > all my ELOG messages? Or is it something I've changed in my local CVS?
>
> You probably started the daemon without redirecting the server logs to a
> file.
>
> Both the server and client were started from the same
hi all. long time.
i spoke w/jan some time ago (in a hurry now -- have to call salvation army
to have them pick up my couch!).
i need to jump in an discuss/get an assignment off the todo list. i am a cs
doctoral student at gmu in va.
i am the best programmer in the world.
i will spend some t
On Wed, 2002-07-17 at 04:36, Christopher Kings-Lynne wrote:
> Hi All,
>
> Has anyone committed something that would cause me to be getting doubles of
> all my ELOG messages? Or is it something I've changed in my local CVS?
You probably started the daemon without redirecting the server logs to a
I have a query and estimations and results don´t
look similar, here is explain analyze:
NOTICE: QUERY PLAN:
Sort (cost=12443.90..12443.90 rows=1
width=93) (actual time=505331.94..505332.67 rows=175 loops=1)
-> Aggregate (cost=12443.88..12443.89 rows=1 width=93) (actual
time=472520.
On Wed, 2002-07-17 at 08:48, Hiroshi Inoue wrote:
> I sent a draft by mistake, sorry.
>
> Hannu Krosing wrote:
> >
> > On Wed, 2002-07-17 at 09:11, Hiroshi Inoue wrote:
> > > Bruce Momjian wrote:
> > >
> > > > From my perspective, when client coders like Dave Page and others say
> > > > they wou
On Tue, 16 Jul 2002 12:23:01 -0400, Tom Lane <[EMAIL PROTECTED]>
wrote:
>I've been thinking that it's really not a good idea to make the OID
>field optional without any indication in the tuple header whether it
>is present. In particular, this will make life difficult for tools
>like pg_filedump
Hi All,
Has anyone committed something that would cause me to be getting doubles of
all my ELOG messages? Or is it something I've changed in my local CVS?
Chris
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archive
On Wed, 2002-07-17 at 09:56, Jan Wieck wrote:
> Joe Conway wrote:
> > The problem is that you would still need to keep a copy of your view
> > around to recreate it if you wanted to drop and recreate a table it
> > depends on. I really like the idea about keeping the original view
> > source handy
On Wed, 2002-07-17 at 09:56, Jan Wieck wrote:
> Joe Conway wrote:
> > The problem is that you would still need to keep a copy of your view
> > around to recreate it if you wanted to drop and recreate a table it
> > depends on. I really like the idea about keeping the original view
> > source handy
On Wed, 2002-07-17 at 08:26, Tom Lane wrote:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > Also, as we have nothing like Oracles ROWNR, I think it will be quite
> > hard to have colnums without gaps in the system views, so we could
> > perhaps have a stopgap solution of adding logical column num
Tom Lane wrote:
>
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > Also, as we have nothing like Oracles ROWNR, I think it will be quite
> > hard to have colnums without gaps in the system views, so we could
> > perhaps have a stopgap solution of adding logical column numbers (
> > (pg_attribute.a
Joe Conway wrote:
> The problem is that you would still need to keep a copy of your view
> around to recreate it if you wanted to drop and recreate a table it
> depends on. I really like the idea about keeping the original view
> source handy in the system catalogs.
This has been the case all the
> -Original Message-
> From: Hiroshi Inoue [mailto:[EMAIL PROTECTED]]
> Sent: 17 July 2002 05:12
> To: Bruce Momjian
> Cc: Christopher Kings-Lynne; Tom Lane; Rod Taylor;
> PostgreSQL-development
> Subject: Re: [HACKERS] DROP COLUMN
>
>
> > >From my perspective, when client coders like
47 matches
Mail list logo
