Greg Stark <[EMAIL PROTECTED]> writes:
> uh, since you asked. I think the logic is that, at least with gcc, -g
> is never harmful since you can compile with -O and -g and then strip
> later if necessary.
Yeah, but ...
> Does it still default to -g with compilers that
> cannot do -O and -g togethe
Andrew Dunstan wrote:
I have wondered (somewhat fruitlessly) for several years about the
possibilities of special purpose lightweight file systems that could
relax some of the assumptions and checks used in general purpose file
systems. Such a thing might provide most of the benefits of a
"dat
On Wed, Oct 15, 2003 at 07:22:56PM -0400, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > 2) Make real separate "short" and "long" descriptions.
>
> We'd have to break the strings freeze to do that. How bad do you want it?
It doesn't take a lot to re-translate, IMO as a trans
Tom Lane wrote:
> While fooling with adding -fno-strict-aliasing to configure, I realized
> that there are still some oddities about its selection of CFLAGS. The
> problems stem from the fact that autoconf will always select a default
> value of CFLAGS that includes "-g", if the compiler accepts "
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Agreed. I like --dump-config. Better to have the verb first.
>
> My only objection to that is that "dump" suggests you will get some kind
> of snapshot of current settings, which is not what this facility does.
I think people will
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Tom> I tend to agree with the opinion that Oracle's architecture
Tom> is based on twenty-year-old assumptions. Back then it was
Tom> reasonable to assume that database-specific algorithms could
Tom> outperform a general-purpose o
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> But I don't see anything
>> wrong with the concept. The short description is also the first
>> sentence of the long description; what's unreasonable about that?
> It constrains the writer of the description in a way he might not s
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Agreed. I like --dump-config. Better to have the verb first.
My only objection to that is that "dump" suggests you will get some kind
of snapshot of current settings, which is not what this facility does.
I don't have an especially good alternative th
While fooling with adding -fno-strict-aliasing to configure, I realized
that there are still some oddities about its selection of CFLAGS. The
problems stem from the fact that autoconf will always select a default
value of CFLAGS that includes "-g", if the compiler accepts "-g" at all.
This has a c
Peter Eisentraut wrote:
> > Actually I think -M -G corresponds to that set of choices. Are we
> > converging on an agreement that we only need that functionality for now?
> > If so, what switch shall be used to get it?
>
> I'm thinking that a completely different option name like --dump-config or
Tom Lane writes:
> > - Who is going to maintain the descriptions in this very special "GNU
> > trick" format?
>
> What's special about it? I now understand that I'd misdescribed it, and
> that the fields ought to be named something like "desc" and "extra_desc"
> rather than "short_desc" and "lo
"murphy pope" <[EMAIL PROTECTED]> writes:
> Did I get (most or any of) this right?
Mostly. A couple of comments: HeapTupleSatisfies can do scankey testing
(that is, see whether columns satisfy "col op constant" conditions) in
addition to the time-qual checking you are thinking about. Also, the
t
James Rogers kirjutas K, 15.10.2003 kell 11:26:
> On 10/14/03 11:31 PM, "James Rogers" <[EMAIL PROTECTED]> wrote:
> >
> > There is some abstraction in Postgres and the database is well-written, but
> > it isn't written in a manner that makes it easy to swap out operating system
> > or API models.
Tom Lane wrote:
James Rogers <[EMAIL PROTECTED]> writes:
If we suddenly wanted to optimize Postgres for performance the way
Oracle does, we would be a lot more keen on the O_DIRECT approach.
This isn't ever going to happen, for the simple reason that we don't
have Oracle's manpower.
[sn
Bruce Momjian wrote:
> At this point, we should probably just do what is needed, and revisit
> for 7.5 --- straight COPY output would probably do the trick.
>
> Now, for a name. I wonder if --config-copy would be OK. It documents
> it is in COPY output format, and it allows us to add a human-rea
In backend/access/heap/heapam.c, there are two functions that I've been
looking at.
The first is heapgettup() and the other is heap_fetch().
I'm guessing that one (heapgettup()) is used for sequential scans and the
other (heap_fetch()) is used to retreive a tuple based on an index entry.
Is t
On Wed, 15 Oct 2003, Stephan Szabo wrote:
> On Wed, 15 Oct 2003, Marc G. Fournier wrote:
>
> > Okay, after feeling stupid about the last one (altho I hadn't thought to
> > read the CREATE INDEX page, only the CREATE SCHEMA one), I really hate to
> > ask this one ... but ... is this documented so
On Wed, 2003-10-15 at 16:20, Robert Treat wrote:
> On Wed, 2003-10-15 at 16:00, Marc G. Fournier wrote:
> >
> > Okay, after feeling stupid about the last one (altho I hadn't thought to
> > read the CREATE INDEX page, only the CREATE SCHEMA one), I really hate to
> > ask this one ... but ... is thi
Marc G. Fournier wrote:
Okay, after feeling stupid about the last one (altho I hadn't thought to
read the CREATE INDEX page, only the CREATE SCHEMA one), I really hate to
ask this one ... but ... is this documented somewhere also:
CREATE SCHEMA company_00244
CREATE TABLE traffic ( ip_id int4, por
On Wed, 2003-10-15 at 16:00, Marc G. Fournier wrote:
>
> Okay, after feeling stupid about the last one (altho I hadn't thought to
> read the CREATE INDEX page, only the CREATE SCHEMA one), I really hate to
> ask this one ... but ... is this documented somewhere also:
>
> CREATE SCHEMA company_002
On Wed, 15 Oct 2003, Marc G. Fournier wrote:
> Okay, after feeling stupid about the last one (altho I hadn't thought to
> read the CREATE INDEX page, only the CREATE SCHEMA one), I really hate to
> ask this one ... but ... is this documented somewhere also:
CREATE INDEX isn't currently a "schema_
Okay, after feeling stupid about the last one (altho I hadn't thought to
read the CREATE INDEX page, only the CREATE SCHEMA one), I really hate to
ask this one ... but ... is this documented somewhere also:
CREATE SCHEMA company_00244
CREATE TABLE traffic ( ip_id int4, port int4, bytes bigint,
Fernando Nasser wrote:
> Bruce Momjian wrote:
> >
> (...)
> > I guess iff someone needs raw with headers in the future, I guess we
> > could add --help-config-raw-headers.
> >
>
> I don't mind if you make it always with the headers. We can easily
> strip the first line when reading the file an
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > One thing that seems very strange about the current API are flags that
> > have meaning only when --help-config becomes before it, as with -G and
> > -M. I have never seen that before,
>
> postgres -boot does exactly that, and the ne
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I understand we want to get something that _isn't_ going to change after
> > 7.4. That's why I proposed a simple --help-config in user-readable
> > format (might be improved in the future), and a --help-config-raw in tab
> > format, w
Marc G. Fournier wrote:
or am I doing it wrong?
ams=# create index company_1.traffic_ip on company_1.traffic using btree (
ip_id ) ;
ERROR: parser: parse error at or near "." at character 27
/Docs on "create index" state:
index_name
/
The name of the index to be created. No sc
On Wed, 2003-10-15 at 13:54, Marc G. Fournier wrote:
> ams=# create index company_1.traffic_ip on company_1.traffic using btree (
> ip_id ) ;
> ERROR: parser: parse error at or near "." at character 27
RTM:
name
The name of the index to be created. No schema name can be
On Wed, 15 Oct 2003 14:54:43 -0300 (ADT)
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
>
> or am I doing it wrong?
>
> ams=# create index company_1.traffic_ip on company_1.traffic
> using btree ( ip_id ) ; ERROR: parser: parse error at or near "." at
> character 27
>
>
> -
or am I doing it wrong?
ams=# create index company_1.traffic_ip on company_1.traffic using btree (
ip_id ) ;
ERROR: parser: parse error at or near "." at character 27
---(end of broadcast)---
TIP 9: the planner will ignore your desire to
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Are you talking about the descriptions in the guc.c file that are part
> of the GUC structures? I think we are heading in a direction where we
> should be pulling descriptions out of SGML like we do with psql help,
> and using that to load the GUC struct
James Rogers <[EMAIL PROTECTED]> writes:
> If we suddenly wanted to optimize Postgres for performance the way
> Oracle does, we would be a lot more keen on the O_DIRECT approach.
This isn't ever going to happen, for the simple reason that we don't
have Oracle's manpower. You are blithely throwing
Is it just me or does pg_dump have no support for dumping conversions at
all?
conversions=# CREATE CONVERSION myconv FOR 'UNICODE' TO 'LATIN1' FROM
alt_to_iso;
CREATE CONVERSION
conversions=# \q
bash-2.05a$ /home/chriskl/local/bin/pg_dump conversions
--
-- PostgreSQL database dump
--
SET SESSIO
Bruce Momjian wrote:
(...)
I guess iff someone needs raw with headers in the future, I guess we
could add --help-config-raw-headers.
I don't mind if you make it always with the headers. We can easily
strip the first line when reading the file and people can easily strip
it piping the output thr
Tom Lane wrote:
Actually, I think the point Peter's been making is that it's not clear
we need a "user-readable" output format at all. The variant you are
calling --help-config-raw is the only one that needs to be supported in
7.4, and anything else should (arguably) be left off so that it doesn't
On Wed, Oct 15, 2003 at 03:56:51PM +0530, Vatsal wrote:
> My query is-
> When can we see Savepoints and Nested Transactions in postgresql
> officially in a stable release?
Certainly not soon. Manfred Koizar and I are doing some work on this
area that we expect to have ready for the 7.5 release.
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> - When the set of GUC properties (when to set, how to set, etc.) change,
> what is the upgrade path? Remember that we change those a lot.
Well, when we add another PGC_ category, that will mean another possible
output value in the column representi
Hi,
I may be a little off -topic asking this here, but then i thought you are the guys working on the bleeding edge and can provide me better insight.
My query is-
When can we see Savepoints and Nested Transactions in postgresql officially in a stable release?
AFAIK in 7.3 release sa
"Bob Badour" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> "Mike Preece" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > [EMAIL PROTECTED] (Dawn M. Wolthuis) wrote in message
> news:<[EMAIL PROTECTED]>...
> > > Bob Badour" <[EMAIL PROTECTED]> wrote in message
> Of course, the big question is why Oracle is even there talking to
> Linus, and Linus isn't asking to get PostgreSQL involved. If you are
> running an open-source project, you would think you would give favor to
> other open-source projects. Same with MySQL favortism --- if you are
> writing an
Nicely spotted, yeah that's what is causing these issue. The reason
-L/opt/local/lib is in there is due to it being ./configured with
--with-libraries=/opt/local/lib and --with-includes=/opt/local/include.
Those configure options are necessary to ensure the configure found the
darwinport-instal
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I understand we want to get something that _isn't_ going to change after
> 7.4. That's why I proposed a simple --help-config in user-readable
> format (might be improved in the future), and a --help-config-raw in tab
> format, without headers.
Actually,
Bruce Momjian <[EMAIL PROTECTED]> writes:
> One thing that seems very strange about the current API are flags that
> have meaning only when --help-config becomes before it, as with -G and
> -M. I have never seen that before,
postgres -boot does exactly that, and the new code was modeled on it.
Wh
Bruce Momjian wrote:
I propose we rip out everything except --help-config -m that shows the
information in the "machine-readable" tab separated format without
headers. If someone can answer the two questions above.
I just proposed that as --help-config-raw. I don't think we want to
head in
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > ... Will Red Hat be upset if we
> > leave it unchanged for 7.4.X and rip this out and redo it in 7.5?
>
> It'd be better if we could get it right the first time, with the
> understanding that the output format is not very negotiable a
Greg Stark wrote:
>
> James Rogers <[EMAIL PROTECTED]> writes:
> > >
> > > Someone from Oracle is on there explaining what Oracle's needs are. Perhaps
> > > someone more knowledgable than myself could explain what would most help
> > > postgres in this area.
> >
> >
> > There is an important dif
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > It'd be better if we could get it right the first time, with the
> > understanding that the output format is not very negotiable at this
> > late hour. But as best I can tell, most of the unhappiness is with the
> > design of the switch set, which
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > ... Will Red Hat be upset if we
> > leave it unchanged for 7.4.X and rip this out and redo it in 7.5?
>
> It'd be better if we could get it right the first time, with the
> understanding that the output format is not very negotiable a
On 10/14/03 11:31 PM, "James Rogers" <[EMAIL PROTECTED]> wrote:
>
> There is some abstraction in Postgres and the database is well-written, but
> it isn't written in a manner that makes it easy to swap out operating system
> or API models. It is written to be portable at all levels. A database
>
48 matches
Mail list logo
