and
> ignore inserts.
No, sorry.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-general mailing list (pgsql-general@pos
gging every single query. By
> the way, I'm using Postgresql 8.3.1 on window xp.
>
> Am I doing something wrong?
The problem is that the checks for the statement type are done at the
time the query arrives from the client, not while executing in a
function.
--
Bruce Momjian <[EMAI
ing and the other is using the timezone meaning.
>
> We don't have much control over the zone definition, so I'm thinking
> maybe the abbrev should be removed from the tznames lists. But that
> seems a bit sucky too. Does anyone have any idea if the zic folk would
> be respo
Russ Brown wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruce Momjian wrote:
> > Scara Maccai wrote:
> >> Hi,
> >>
> >> I was looking at the TODO:
> >>
> >> http://www.postgresql.org/docs/faqs.TODO.html
> >>
is complicated... it's obviously
> used for a lot of other things... could you use another character?
I think a search for ' -' will show you the items you want.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
ill executed. Kill was never officially supported as a way to
terminate a backend, but it will be in 8.4 and there is an SQL function
to do it too.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your
size_t not int, but I have a feeling there are a lot of other similar
> gotchas when running this code on a 64-bit machine. We use int
> arithmetic an awful lot for stuff that probably should be size_t
> or ssize_t ...
I assume this is not a TODO item.
--
Bruce Momjian <[EMAIL
Alvaro Herrera wrote:
> Bruce Momjian escribi?:
> > Dan Dascalescu wrote:
> > > I'd like to submit a correction for question "2.1) How do I setup a
> > > datasource?" in the FAQ. The existing text reads:
> > >
> > > "For Windows, us
t;
>
> On Windows XP, however, there is no Control Panel applet for ODBC
> management. The answer should read:
>
> "Go to Programs -> Administrative Tools -> Data Sources and Add the
> PostgreSQL Unicode driver".
Uh, I am not sure where you saw this FAQ but
e pg_dump should disable
> >> statement_timeout when it runs.
> >
> > You mean like this?
> >
> > http://archives.postgresql.org/pgsql-committers/2008-05/msg00026.php
>
> Very cool. I assume it's not in 8.3.3 then?
No, because this is a functionality change, rather than
> space in the db as it does in a flat file. that's just an
> approximation. The actual size of each type etc is defined in the
> other links in this thread.
Folks, we have an FAQ about this:
http://www.postgresql.org/docs/faqs.FAQ.html#item4.5
--
Bruce Momjia
ing this feature
> >> into Postgres?
> >
> > Probabably --- it seems like a narrow use case.
>
> I'll consider this to be the definite answer unless I hear a dissenting
> opinion in the next few days.
Yea, I might be wrong.
--
Bruce Momjian <[EMAIL PROTECT
uld make sense to reuse the SIGALARM signal used by
> statement_timeout to forcibly close the Postgres connection when
> the watchdog triggers.
Not too hard.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterpr
8.3 bu you can use
query_cancel stop terminate the query. 8.4 will have this capability.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
S
o accept more liberal DOCTYPE specifications
http://archives.postgresql.org/pgsql-general/2008-02/msg00347.php
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can
s about, either.
Don't forget adding a blank line between quoted text and your reply;
that is helpful too.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be
design
> or an oversight?
Will be fixed in 8.4.
> Also, what would be the feasibility of having psql route output to the
> pager if the output is too long or too _wide_? I end up with too wide at
> least as often as too long.
Also done for 8.4.
--
Bruce Momjian <[EMAIL
doesn't yet handle
> error cases. How liberal should we be about capitalization, spelling,
> etc.?
Please try ParseVariableBool() in psql/variables.c, and use diff -c.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://en
beyond a second?
>
> I am looking at tens of millions of rows, which is why my predecessor may
> have used integer to store epoch to save space.
Our timestamp has a much larger range than a 4-byte time_t, docs say:
4713 BC
294276 AD
--
Bruce Momjian <[EM
extension of existing ts_headline.
>
> --
> Teodor Sigaev E-mail: [EMAIL PROTECTED]
> WWW: http://www.sigaev.ru/
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make chang
nks.
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Yep, updated:
> > * Allow adding/removing enumerated values to an existing enumerated
> > data
>
> Renaming an existing value might be interesting too (and would be far
> easier than
Matthew T. O'Connor wrote:
> Bruce Momjian wrote:
> > Matthew T. O'Connor wrote:
> >> D. Dante Lorenso wrote:
> >>> Or, here's another way to look at it ... make it easier to modify ENUM
> >>> datatypes because we all know that you w
r way to look at it ... make it easier to modify ENUM
> > datatypes because we all know that you will eventually need that
> > feature whether you males, females, and unknowns think so or not.
>
> +1
Added to TODO:
* Allow adding enumerated values to an existing enumerated data
ces (the english FAQ) talk about "major releases" happening every
> year and "minor releases" happening every few months, but without defining
> what that means to the numbering.
>
> Perhaps there should be a FAQ that says that our numberin
some people mentioning they were using Micro Focus cobol and
Postgres:
http://search.postgresql.org/search?q=cobol+micro+focus&m=1&l=&d=-1&s=r
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enter
>
> Any hints?
>
> ---(end of broadcast)---
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>choose an index scan if your joining column's datatypes do not
>match
--
Bruce Momjian <
8.3 docs on the subject:
http://www.postgresql.org/docs/8.3/static/ssl-tcp.html
http://www.postgresql.org/docs/8.3/static/libpq-ssl.html
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If y
minutes' -
interval '29 hours');
justify_hours
---
10:30:00
(1 row)
There have been good arguments that justify_hours() behavior should be
the default.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
pg' in part of the command, with no underscores, and it matches the
existing command that already have 'db'.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can
Clodoaldo wrote:
> According to Slashdot IBM is investing in EnterpriseDB. What does it
> mean for Postgresql?
There should be no affect on the community, except that EnterpriseDB
might be able to support the community a little better because of a
little more funding.
--
Bruce M
to a debate about why we can't add triggers to catalog
> tables; forgetting that there's other ways to do this. Searching the
> pgsql-hackers archives should be enlightening.
We have a potential patch for 8.4 for this.
--
Bruce Momjian <[EMAIL PROTECTED]>http:/
M would probably make the problem
> go away (for awhile, until the index reaches 4GB).
>
> In the long run, for queries inserting many rows it might be interesting
> to accumulate all the entries intended for a btree index and sort them
> before inserting. Not sure about possible
---(end of broadcast)-------
> TIP 2: Don't 'kill -9' the postmaster
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a h
e database schema and restoring it to a new schema? This seems more
> like a part that should be under strict user control and not automated
> by common queries.
No one has actually asked for CREATE SCHEMA LIKE before but we could add
it to the TODO list if we can find a few people who wan
se a
> > bit string is a varlena type.
>
> Wow, that's screwed up... that's a lot more than varlena overhead:
>
> select pg_column_size('a'::text), pg_column_size(1::numeric),
> pg_column_size(3111234::numeric);
> pg_column_size | pg_column_size | pg_column_size
> ----+--
re communicate & market in style.
> Visit us online at http://www.myemma.com
>
>
>
> ---(end of broadcast)---
> TIP 6: explain analyze is your friend
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
Enter
> probably stick with a Python implementation outside the SQL query.
> >
> > Thanks for your answers.
> >
> > --
> > Catalin
> >
> > ---(end of broadcast)---
> >
> > TIP 5: don't forget to increase your free space map
-
> Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC
> "El d?a que dejes de cambiar dejar?s de vivir"
>
> ---(end of broadcast)---
> TIP 5: don't forget to increase your free space map settings
--
Bruce Momjian <[EMAI
make their way back into the open source
> > product, some
> > only even go to paying customers).
>
> This is something I noticed too when looking at MySQL and postgres.
> The frequency of bug fixes and features, some coming over pretty
> quickly from the community release
ocess at a fixed location that just
> > happens to already be occupied by a dll that Windows had decided to
> > relocate?
>
> Not that wild a guess, really :-) I'd say it's a very good possibility -
> but I have no idea why it'd do that, since all backends load the
>
> ---(end of broadcast)---
> TIP 1: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to [EMAIL PROTECTED] so that your
>message can get through to the mailing list cleanly
--
Br
-(end of broadcast)-------
> TIP 4: Have you searched our list archives?
>
>http://archives.postgresql.org/
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.ent
ce:
> >
> >
> > 1. stop standby postgres server
> > 2. [optional] preserve data directory, remove unnecessary WAL files
> > 3. restart standby server
>
> step 2 only.
>
> Clearly not an optional step, since its a 1 stage process. :-)
>
> --
> Simon Rigg
RUNCATE a table because triggers are not
> called, and the table is locked in exclusive mode.
>
> It was easy, so I can update the patch as necessary until it can be
> submitted.
>
> Thanks,
>
> ...Robert
>
> ---(end of broadcast)-----
CREATE TABLE distributors (
did integer CONSTRAINT no_null NOT NULL,
namevarchar(40) NOT NULL
);
Added to TODO:
o Have CONSTRAINT cname NOT NULL record the contraint name
Right now pg_attribute.attnotnull records the NOT NULL st
tml and there are
> only entries for 38.7.5.1 through 3...
You mean you only see 38.7.3 but 38.7.3.5 is there but just not listed
at that level of detail.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enter
uld do it regardless of
> backend encoding.
With Tom's encoding() patch applied I assume there is no TODO item here.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ I
s secure database.
>
> Is this something worth considering adding as a feature to Postgres?
No. Most people who need this use schemas. Frankly, if you can do
cross-db queries you are kind of losing the security value.
We do have /contrib/dblink that does cross-db queries.
--
Bruce Mom
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Scara Maccai <[EMAIL PROTECTED]> writes:
> >>> I got that there should be no difference... plus, I don't get any
> >>> errors,
> >>
> >
, but you seem to have managed to find a
> sequence of operations that avoids those checks. Turning a table into a
> view with a manual CREATE RULE operation has always been a kluge, and
> it's missing a check that the table isn't part of an inheritance tree.
Is this a TODO? Seem
seen.
> What OS is this on, what's the version of ps?
I had forgotten we showed the remote port number for TCP connections,
but I see it here:
postgres 13651 8991 0 7:26AM ?? 0:00.01 postgres test 127.0.0.1(57352)
idle (postmaster)
and it seems we have been doing it for ye
stgres?
Not possible --- many data types are of variable length.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
e worst
we should have a way for us to upgrade the older version of pg_dump with
whatever functionality we need and just tell people to be running the
most recent minor release before upgrading.
What cases on the past have needed the new pg_dump?
--
Bruce Momjian <[EMAIL PROTECTED]>
we made versions EOL and they can interpolate
from there.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---(
ar reports. We don't actually recommend
hyperthreading usually.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
the most current
information from the mailing lists.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
-
d
developers, while Postgresql Conference East/West are more end-user
conferences.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ
oadcast)---
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>choose an index scan if your joining column's datatypes do not
>match
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
Enterpri
it is a single benchmark, I have never seen such a
clear comparison between Postgres versions, and the 8.2->8.3 improvement
is huge, +38% improvement.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprised
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> On Fri, Jan 04, 2008 at 09:31:41AM -0500, Bruce Momjian wrote:
> > Unfortunately, this is on our TODO list as something we are not planning
> > to do:
> >
> > * Allow AS in "SELECT col AS l
tional (not wanted)
Because we support postfix operators, it isn't possible to make AS
optional and continue to use bison.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.e
ry would improve performance.
I have added this to TODO:
* Allow multiple identical NOTIFY events to always be communicated to
the
client, rather than sent as a single notification to the listener
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
et lost.
>
> In case we want to send extra text messages with NOTIFY, we should make
> sure, that no notify get lost.
Agreed.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If y
ck notification details by reading tables.
TODO already has:
* Add optional textual message to NOTIFY
This would allow an informational message to be added to the notify
message, perhaps indicating the row modified or other custom
information
x/bsd/unix/windows differences in
> section similar to the User Comments sections of the documentation.
Can you give a specific example? As I said we simulate Windows so it
should act just like Unix.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > Huh, why is it awkward?
> > >
> > > Alternatively, you can send the signal directly using kill
> > > (or pg_ctl kill TERM [process id]).
> >
> > I
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Howard Cole wrote:
> > >
> > > >>>> Which you can do, no? I thought pg_ctl's kill option was invented
> > > >>>> specifically to make this less painful on Windows.
> >
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > We used to have the C defined MAKE_EXPIRED_TUPLES_VISIBLE that would
> > make deleted rows visible, but it seems it was removed in this commit as
> > part of a restructuring:
>
> It was removed be
n't want to trim the
email because it has context that might be needed for the reply, and
bottom-posting just makes it harder to find my question, and the
question isn't really related to the content of the email.
--
Bruce Momjian <[EMAIL PROTECTED]>
docs:
Alternatively, you can send the signal directly using kill
(or pg_ctl kill TERM [process id] on Windows).
You can actually use pg_ctl kill on Unix too but it seems awkward to
suggest it in the existing sentence.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
up.
Looks OK now:
http://www.postgresql.org/docs/8.3/static/release-8-3.html
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Itagaki Takahiro and Tom Lane
Not sure if we should re-add it for later use.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Chri
it before permitting the next?
They proceed in parallel. Backends wait only on specific rows that
conflict, not the index page.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If
x27;t exceed 4 billion commands.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---(end of broadcast)---
Jeff Trout wrote:
> iirc, didn't some big us govt group move to PG from Informix? I
> think Bruce mentioned something once about that..
US National Weather Service changed 170 weather sites from Informix to
Postgres. Postgres worked well for them.
--
Bruce Momjian <[E
server who I grand access and who I don't even if they are
> who they claim they are. And this based only on certificates not user /
> pass or other mechanisms like LDAP / PAM.
Have you tried adding CRLs? We support those.
--
Bruce Momjian <[EMAIL PROTECTED]>
Kevin Kempter wrote:
> Hi List;
>
> I know that the default case for postgres (psql) on Linux/*ix platforms is
> lowercase. I wonder is this also true on Windows platforms?
Yes.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB
datatype-money.html
Basically MONEY had some major limitations but now someone is working on
improve it so we probably will keep it.
We still have these TODO items for MONEY:
* Add locale-aware MONEY type, and support multiple currencies
http://archives.postgresql.org/pgsql-general/2005-08/
ithout giving up most
> of the performance advantages of temp tables.
TODO updated:
* Prevent long-lived temporary tables from causing frozen-xid advancement
starvation
The problem is that autovacuum cannot vacuum them to set frozen xids;
only the session that crea
> probably stick with a Python implementation outside the SQL query.
> >
> > Thanks for your answers.
> >
> > --
> > Catalin
> >
> > ---(end of broadcast)---
> >
> > TIP 5: don't forget to increase your free space map
l do something like
that.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---(end of broadcast)
want to do with it. XML is quite a broad topic.
Here is our Postgres 8.2 documentation about XML:
http://www.postgresql.org/docs/8.2/static/datatype-xml.html
Postgres 8.3 has some new XML features:
http://www.postgresql.org/docs/8.3/static/release-8-3.html
--
Bruce
ed with them about that article
> and although it isn't exactly accurate, it is close enough and is a
> positive endorsement of our project.
Oh, yea, that article. There was some confusion by the author over 3rd
party stuff vs main project stuff. It was a "stuff-is-coming" ar
retty much
tell you everything you need.
---
>
> Regards
> Dhaval
>
> On Nov 14, 2007 10:44 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > Dhaval Shah wrote:
> > > I am on 8.2 produc
http://www.2ndQuadrant.com
> >
> >
> > ---(end of broadcast)---
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> >choose an index scan if your joining column's datatypes do not
> >match
Scott Marlowe wrote:
> On Nov 9, 2007 4:57 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > Jeff Larsen wrote:
> > > > Is there any way to query the database to identify what the current
> > > > connections are (connections, sessions, or whatever you want to
Jeff Larsen wrote:
> > Is there any way to query the database to identify what the current
> > connections are (connections, sessions, or whatever you want to call them)?
>
> select * from pg_stat_activity;
Is this an FAQ?
--
Bruce Momjian <[EMAIL PROTECTED]>
item", and put a dashed line under my text so people realize
I top-posted and there is nothing new below my text.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard
t;
> This seems like the key to unlocking your new functionality for most
> people.
You already have that control at the SQL SELECT level so you are just
avoiding typing to add the GUC parameter. I think we need more requests
for such a feature before we add it.
--
Bruce Momjia
cash_words
One hundred dollars and zero cents
(1 row)
but that is money-oriented.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> >
> > Is this item closed?
>
> No, it isn't. Please add a TODO item about it:
> * Prevent long-lived temp tables from causing frozen-Xid advancement
>starvation
Thanks. Added to TODO.
--
Bruce Momjian
Tom Lane wrote:
> Steve Crawford <[EMAIL PROTECTED]> writes:
> > My vote is to add "Appendix I. Abbreviations".
>
> It seems more like FAQ material than something for the manual.
I prefer the manual. I would think the list would be pretty long and
deal with lots o
this:
http://www.postgresql.org/developer/ext.backend.html
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Ben wrote:
> Woah, when did that come around? Talk about sweet syntactic sugar
8.2
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be yo
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> This is silly. Have you forgotten that the max number of columns is
> >> constrained to 1600 on the backend side?
>
> > Uh, this is the number of returned rows, r
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Greg Sabino Mullane wrote:
> >> There may be some other safeguards in place I did not see to prevent this,
> >> but I don't see a reason why we shouldn't use unsigned int or
> >> u
rns an integer result, large result sets might overflow the
return value on 32-bit operating systems.
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ ca
ee a reason why we shouldn't use unsigned int or
> unsigned long int here, both for ntups and the return value of the
> function.
I think we need more use cases before we break the API on this one.
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB
Andrew Hammond wrote:
> On 9/13/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> >
> > Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > >
> > > > Is this item closed?
> > >
> > > No, it isn't. Please add a TODO i
601 - 700 of 2011 matches
Mail list logo
