You should see a lines like this in configure.in
[lines 28-33 of configure.in for 7.2.4]
AC_PREREQ(2.13)
AC_CONFIG_AUX_DIR(config)
VERSION='7.2.4'
AC_SUBST(VERSION)
AC_DEFINE_UNQUOTED(PG_VERSION, "$VERSION")
best wishes
Mark
bpalmer wrote:
I'm trying to figure out what version of a source code
Joshua D. Drake wrote:
> Hello,
>
> I might be wrong on this but I think that ecpg using transactions by
> default for each query.
> Perhaps turning on autocommit?
Yep, use:
EXEC SQL SET AUTOCOMMIT = ON;
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PRO
Jeff wrote:
UNless the controller itself has a battery backed cache it is dangerous - there
are many more failures than losing power. Ie, blowing out the power supply or cpu.
We've burnt up a fair share of cpu's over the years. Luckly on a Sun it isn't that
big a deal.. but on x86. wel... yo
Furthermore, if the disk drives are lying to the controller, it's
anybody's guess whether or not data ever actually gets to the disk.
When is it safe to let blocks expire out of the controller cache?
If your computer can't know if the data has been written (because of
drives that lie), I can't im
>
> > I'm trying to figure out what version of a source code I have. I know
> > it's a 7.2 release, but how can I find out of it's 7.2, 7.2.3, 7.2.4,
> > etc. FROM THE SOURCE CODE, not from compiling (it doesn't compile, it's
> > testing code).
>
> grep VERSION configure
I did try that,
On Sat, 15 Nov 2003, bpalmer wrote:
> I'm trying to figure out what version of a source code I have. I know
> it's a 7.2 release, but how can I find out of it's 7.2, 7.2.3, 7.2.4,
> etc. FROM THE SOURCE CODE, not from compiling (it doesn't compile, it's
> testing code).
grep VERSION conf
> Whoa! You mean these aren't already separate database clusters or even
> separate systems? I am very shocked, you can't do a proper Dev --> QAT
> --> Prod environment if all three systems are run by the same
> postmaster, or on the same host imo.
I can see having separate clusters would save me
On Nov 13, 2003, at 2:47 AM, Brett Maton wrote:
Thanks for the answers guys,
I ran a quick query lastnight select length(data) from pg_largeobject
where loid = which prompted my post.
The query returned 'n' rows of 2048 bytes and an incomplete "page"
of say
236, as I wasn't really thin
On Tue, Nov 11, 2003 at 03:38:53PM -0500, Christopher Browne wrote:
> In the last exciting episode, [EMAIL PROTECTED] (Jan Wieck) wrote:
> > I look forward to your comments.
>
> It is not evident from the paper what approach is taken to dealing
> with the duplicate key conflicts.
>
> The example:
On Wed, 12 Nov 2003, Reece Hart wrote:
> On Wed, 2003-11-12 at 09:04, jake johnson wrote:
>
> > I also posted about the performance increase of 7.4, but I think that
> > much of the difference you're seeing (because it's such a large
> > difference) is probably due to the cleanliness of a newly
Richard Huxton wrote:
> On Thursday 13 November 2003 11:16, Alvaro Herrera wrote:
> > On Thu, Nov 13, 2003 at 09:34:27AM +, Richard Huxton wrote:
> > > On Thursday 13 November 2003 04:52, Craig O'Shannessy wrote:
> > > > So, what ever happened to the "RedHat database"? I though RH was going
>
Rajesh Kumar Mallah writes:
> *1.* Suppose varchar(30) turns out to be too small oneday
> and we want to increase it to varchar(100) , what do i do ?
This is no different from the problem of changing a column type in place.
It's still being worked on.
> *2.* Its difficult to see all the con
Hi ,
I think one of the usage patterns of DOMAINS is
to have size specifications and validity constraints
at one place for easy administration of Database.
Eg, instead of declaring email to be varchar(30) in
10s of tables and putting a CHECK constraint for
presence of '@' we could dec
Just a question... Are there any reasons not to just take the source and
compile it under RHEL 3.0? Or am I missing something?
(We are about to install 3.0, so I would really like to know..)
BTJ
On Thu, 2003-11-13 at 16:08, Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > The RHEL3 b
Its really nice to see/read the pretty printing of
VIEW definations!! in 7.3 it was a
nightmare to see definations of long views.
Kudos to the TEAM.
Regds
Mallah
tradein_clients=# \d XYZ
View XYZ
Column | Type | Modifiers
-+---+-
Peter Eisentraut wrote:
Rajesh Kumar Mallah writes:
*1.* Suppose varchar(30) turns out to be too small oneday
and we want to increase it to varchar(100) , what do i do ?
This is no different from the problem of changing a column type in place.
It's still being work
On Thu, 13 Nov 2003, jini us wrote:
> Hi,
>
> I am starting a new project where I intend to use
> embedded database server in my win32 application.
> I intend to use VC++ microsoft studio 6.0 as my
> development environment.
>
> The postgres.org website seems to be catering for
> people with all
On Wed, 12 Nov 2003, Rick Gigger wrote:
> Is this correct?
>
> vacuum by itself just cleans out the old extraneous tuples so that they
> aren't in the way anymore
> vacuum analyze rebuilds indexes. If you add an index to a table it won't be
> used until you vacuum analyze it
> vacuum full actual
On Fri, 14 Nov 2003 23:43:26 +0530
Rajesh Kumar Mallah <[EMAIL PROTECTED]> wrote:
>
> BTW: Searching on archives.postgresql.org takes ages is it using FTS?
>
Groups.google.com has indexes of the mailing lists so you can use that
to search. I do because archives is unusably slow.
you know. we
> > Is this correct?
> >
> > vacuum by itself just cleans out the old extraneous tuples so that they
> > aren't in the way anymore
>
> Actually it puts the free space in each page on a list (the free space
> map) so it can be reused for new tuples without having to allocate
> fresh pages. It finds
Does anyone have any experience with postgres on fedora?
---(end of broadcast)---
TIP 8: explain analyze is your friend
21 matches
Mail list logo
