mlocked pages when the process which had the page locked dies, especially
if it crashes. Or that some versions of some OSes are simply buggy. It's not
like it's a case that would ever be tested or even noticed if it failed.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
again.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
Andrew Dunstan [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
With the branch delayed they will have to say Oh, there's a new
release. I wonder when they will branch so I can start building the new
branch.
No, I wrote
would be responsible for combining the result
just as it is with the MCV estimates.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 7: You can help
Gregory Stark [EMAIL PROTECTED] writes:
So I had a thought about how to soften the controversial hard cutoff of 100
for the use of the histogram selectivity. Instead of switching 100% one way or
the other between the two heuristics why not calculate both and combine them.
The larger
. Otherwise you're going to write a patch and then
have two trees and be searching around in the dark for a difference.
This strikes me as something dtrace might be able to help measure.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services
realize that bash
itself is one such large program...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 4: Have you searched our list archives
a lot
of work.
It's evidently guessing wrong about the limit being satisfied early. The
non-indexed restrictions might be pruning out a lot more records than the
planner expects. Or possibly the table is just full of dead records.
--
Gregory Stark
EnterpriseDB http
3 | 91904
4 | 89058
5 | 87001
(5 rows)
postgres=# fetch backward 5 from c;
i | r
---+--
4 | 89058
3 | 91904
2 | 15034
1 | 10352
(4 rows)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services
or
not regardless of how you refer to it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 6: explain analyze is your friend
TABLE
ALTER COLUMN TYPE). The defining characteristic of DDL is not that it doesn't
modify the data but that it does modify the table definition.
By that definition CLUSTER is DDL and TRUNCATE is DDL if you look at the
implementation rather than the user-visible effects.
--
Gregory Stark
-unsupported-incompatible-connections
1/2 :)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
of some data types that mapped every value to
a floating point value. I suppose we could add that as a btree proc entry for
specific data types but it would be a pretty radical change.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony
ourselves that there normally wasn't any cost associated with a
high default_statistics_target, we could increase the default, which
would reduce the amount of traffic we'd see on -performance about bad
query plans.
I suspect we could raise it, we just don't know by how much.
--
Gregory Stark
a full index scan though. And it doesn't help for columns which
aren't indexed though I'm not sure we need this info for columns which aren't
indexed. It's also not clear how to interpolate from that the amount of random
access a given query would perform.
--
Gregory Stark
EnterpriseDB
is a plain anyarray like normal, but the array_accum call would look at the
call site and stash the actual contents there in a linked list or tuplesort?
The actual anyarray data type would just have a flag saying the data's over
there.
--
Gregory Stark
EnterpriseDB http
of escape hatch for pg_dump to request real
physical order when dumping clustered tables.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 7: You
Robert Treat [EMAIL PROTECTED] writes:
the idea of implementing row level visibility in statement level triggers
Huh?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast
DDL except during a
maintenance window for example.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please
of a heavyweight-lock acquisition.
Is that the flag that is an assertion that no cleanup is needed? Or is that
something else?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast
is going
to stop another process from being able to issue reads against the same file
until those megabytes are all in kernel cache, let alone if they overflow
cache and force i/o.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication
errors and resume the outer transaction.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project
to uninstall all 700+ other packages.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 5: don't forget to increase your free space map
Tom Lane wrote:
%install
rm -rf $RPM_BUILD_ROOT
make DESTDIR=$RPM_BUILD_ROOT install
I hope nobody tries building in a directory with a space in it...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support
that cleanly you have to run configure once
for each architecture and build each architecture with the appropriate
config.h.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end
Simon Riggs [EMAIL PROTECTED] writes:
On Sat, 2008-01-12 at 18:46 +, Gregory Stark wrote:
To do something like that the user would have to create a prepared
transaction
to save the snapshot. I think that makes sense though since effectively it's
just requiring that the user explicitly
I perhaps not with pgadmin itself
which I think follows the Postgres release cycle).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast)---
TIP 9
would need to be able to break them up by process.
So two processes writing to the same table would be able to write to different
WAL logs.
That sounds hard but I'm not sure. It may not be as bad as it sounds.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
)
postgres=# select (array['{foo}'::text[],'{bar}'])[1];
array
---
(1 row)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 5: don't forget
in
minutes. As a result data warehouse reports could be delivered the same night
instead of being hours, and in some cases days, delayed.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end
Markus Schiltknecht [EMAIL PROTECTED] writes:
Hi,
Gregory Stark wrote:
In a previous life I had a database which had daily partitions. I assure you
it was unquestionably the right decision. Each day's data wasn't just
distinguished by the timestamp but actually was entirely separate from
be made explicit.
But this is not a strong opinion.
I had another thought. Perhaps in use_assert_checking mode we should have it
start from a random position every time. Or perhaps just a random position
from amongst the first n pages.
--
Gregory Stark
EnterpriseDB http
this in beta. Thanks a lot to Hannes Dorbath for
testing and reporting it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast)---
TIP 7: You can help support
:-(
Perhaps we ought to have made heap_beginscan guarantee an ordered scan and
made synch scans be explicitly requested. That would have touched a lot of
lines but been more conservative. I'm not sure it's worth going back on it now
though.
--
Gregory Stark
EnterpriseDB http
of
action-at-a-distance.
In Postgres the performance consequence is reversed. We have a performance
*hit* for security definer. And the pl interpreters don't behave any
differently as far as when they do their lookups.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
having the snapshots expire.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
files.
That's not the only reason for out-of-tree builds. Packagers often find it
easier to build out-of-tree since it means they can generate a clean diff
against the original source.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres
of your records
and the relative length of your transactions versus transaction rate. The TPCC
experience is with ~ 400 byte records and many short transactions.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
Simon Riggs [EMAIL PROTECTED] writes:
On Wed, 2008-01-09 at 02:25 +, Gregory Stark wrote:
Without naming the DBA would have to specify the same ranges every time he
wants to change the properties. He might do a SET read_only WHERE created_on
'2000-01-01' one day then another SET
of it that's not going to help at all.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
clauses when we have multiple variables which come out to the
same value?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 1: if posting/reading
the next best option.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating
to avoid an infinite loop) could be
possible.
I am hoping our other things which ignore VACUUM such as the globalxmin
calculation are careful not to ignore VACUUM ANALYZE processes?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres
masse to it
(such as dropping it) at some later date.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 6: explain analyze is your friend
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
I didn't have any luck reproducing either of these behaviors --- maybe
it's data-dependent. Can you extract a test case?
I haven't been able to reproduce this either but I produced an entirely
different problem
Gregory Stark [EMAIL PROTECTED] writes:
On the other hand we can't just ignore all vacuums because someone could issue
a manual vacuum inside a transaction (I think?).
Doh, ignore this. sigh.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce
guess the combination
is lethal.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 6: explain analyze is your friend
Gregory Stark [EMAIL PROTECTED] writes:
Joshua D. Drake [EMAIL PROTECTED] writes:
On Mon, 7 Jan 2008 11:58:29 -0500 (EST)
Bruce Momjian [EMAIL PROTECTED] wrote:
I assume it is this TODO item:
o Prevent long-lived temporary tables from causing frozen-xid
advancement
table.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan
person_to_event_person_type_fkey
cannot be implemented
DETAIL: Key columns person_type and person_type are of incompatible types:
person_type_new and text.
I get the same thing if it's an integer field.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication
dealing with smaller mss and much higher
protocol overhead. You also lose bulletproof authentication from unix
credentials and are instead relying on properly configuring your network
authentication. And it's much easier to accidentally be relying on insecure
identd.
--
Gregory Stark
directly from the
file.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
a *fascinating* idea. I'm having trouble coming up with a really
killer use case for it since the bounded heap sort takes care of many cases
where it would seem to apply. But it seems rally promising.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 6: explain analyze is your friend
could call
getsockopt(SO_PEERCRED) to verify you're really connected to a process run by
postgres. But that isn't going to work if the postgres user could be named
something else. In that case what is it you want to verify though?
--
Gregory Stark
EnterpriseDB http
see in the image below.
Não remova a próxima linha / Don't remove next line
captchakey:asbEJKOW1nbXcwMTY4Mjk
---End Message---
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end
actually *designed* to do that you
really need to get that software removed from your machine.
I was under the impression though that this was just how open worked on
windows. Only one process can have a file open at the same time.
--
Gregory Stark
EnterpriseDB http
of misconfigured mail software addreses from infotecnica.com.br are
banned from pgsql mailing lists. Please contact your postmaster to request
they fix the problems
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support
by your disk bandwidth, not your cpu speed.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
query will run faster but you won't be able to
run as many simultaneously without having them slow back down. And the
overhead of parallelizing the query will be a net loss.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services
and
Greenplum customers.
Surely such machines have kickass memory backplanes too though? How could it
ever be reasonable to have an i/o controller with more bandwidth than your
memory?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres
Decibel! [EMAIL PROTECTED] writes:
Also, has anyone looked into adding a class of system calls that would
actually tell us if the kernel issued physical IO? I find it hard to believe
that other RDBMSes wouldn't like to have that info...
Yeah, I think that's called DTrace
--
Gregory
the
true near-zero rate of cache misses.
We could mitigate that somewhat by describing it in the plan as something like
... (... I/O fast=nnn slow=nnn)
instead of the more descriptive physical and logical
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
works. *_deform_tuple has to be able to deal with tables
to which people have added columns. In that case tuples inserted before the
columns were added will look just as you describe, with trailing columns
missing.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Andrew Dunstan [EMAIL PROTECTED] writes:
Interesting. Maybe forever is going a bit too far, but retrying for n
seconds or so.
I think looping forever is the right thing. Having a fixed timeout just means
Postgres
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
).
But I do think that showing logical I/Os without even an heuristic based
measurement of actual physical i/o is pretty useless. It will make people
think they want to grow their shared buffers to cover all of memory.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
On Dec 14, 2007 6:42 PM, Tom Lane [EMAIL PROTECTED] wrote:
How do people feel about applying this to 8.3, rather than holding it?
I think it would have been better to apply before beta. We would have found
out
could print a warning after 30s but then I think you have to keep trying
forever. Just like database operations hang forever waiting for a lock.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support
hundreds or thousands of times per minute. A WARNING
is effectively an ERROR.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 1: if posting
= ANY ('{100,1000}'::integer[]))
- Bitmap Index Scan on hi (cost=0.00..8.52 rows=2 width=0) (actual
time=74.539..74.539 rows=2 loops=1 logical-I/O=2 physical-I/O=2))
Index Cond: (i = ANY ('{100,1000}'::integer[]))
Total runtime: 87.820 ms
--
Gregory Stark
EnterpriseDB
as today, so it
would seem a slushy freeze at best.
FWIW, I'm good with applying it to 8.3.
I think it would have been better to apply before beta. We would have found
out if users were going to complain about it. Perhaps we should do it for 8.4
instead
--
Gregory Stark
EnterpriseDB
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2007-12-13 at 06:27 +, Gregory Stark wrote:
Heikki proposed a while back to use posix_fadvise() when processing logs to
read-ahead blocks which the recover will need before actually attempting to
recover them. On a raid array that would bring
to or if there are practical problems which
would have to be solved to do so.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 6: explain analyze
arrange to pass over a reference to the whole
hash.
I fear the real complexity would be (as always) in the planner rather than the
executor. I haven't really looked into what it would take to arrange this or
how to decide when to do it.
--
Gregory Stark
EnterpriseDB http
way, I think that the change is valid and we need to do it.
When do we normally freeze strings?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast
files dump out that hash in a second file alongside.
PITR recovery could read that in before it starts reading any file and consult
it before applying any records.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support
something to run it faster. The problem
with this situation is that buying a faster raid controller doesn't help you.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast
that that doesn't work I don't see any particular reason to accept
negative offsets or limits in 8.4 and on.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast
this and send them
off to index_getmulti() as a group. That would make it more important to do
the above in the right order since a big part of the advantage of doing that
would be avoiding the redundant index descents for adjacent index keys.
--
Gregory Stark
EnterpriseDB http
will almost always turn the partition scans into parallel scans and
use separate processors to scan different partitions.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast
will be magically
losing their share locks if you turn off the read-only flag. Do you need to
obtain an exclusive lock on the table to turn it read-write?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
. If on the other hand you just mean a
simpler more regular structure than turing-complete constraints then I would
agree, but for the reasons above -- not for the problems with hash/bin
partitioning and equality semantics.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Gregory Stark [EMAIL PROTECTED] writes:
I think this will be easiest to do for bitmap index scans. Since we gather up
all the pages we'll need before starting the heap scan we can easily skim
through them, issue posix_fadvises for at least a certain number ahead of the
actual read point
be harder to optimize the our
current COPY can be optimized.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
and I don't see any more general solution.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 5: don't forget to increase your free space map
Tom Lane [EMAIL PROTECTED] writes:
When Tom Lockhart was around the project it was even messier, since he and I
shared not only the same first name but all three initials.
Then there's Greg Stark, Greg Smith, and Greg Sabino (Mullane).
Perhaps we should just go by uid.
--
Gregory Stark
there were so I can get a feel for the magnitude of the
improvements between versions.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast)---
TIP 5: don't
user name and prompting for a password because the server
requires it are really two different things.) You are encouraged to look
at the -U and -W options instead.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support
%2976%3A4%3C380%3AWATCAO%3E2.0.CO%3B2-Psize=LARGEorigin=JSTOR-enlargePage
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 6: explain analyze
authentication for your
postgres server then that means you have to specify the user on the command
line all the time.
Don't actually have a psql built with kerberos authentication handy but I'll
try to remember to test this the next time I do.
--
Gregory Stark
EnterpriseDB http
this in c.h:
#ifdef WIN32
#ifndef _USE_32BIT_TIME_T
#error Postgres uses 32 bit time_t add #define _USE_32BIT_TIME_T on Windows
#endif
#endif
For modules which *do* use time_t this is safer. However for modules which
don't use time_t it'll be an unnecessary hassle.
--
Gregory Stark
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Josh Berkus [EMAIL PROTECTED] writes:
I've just noticed that pg_controldata doesn't say anything about whether
the database is 64-bit or 32-bit.
That's because there is no such concept.
I think the relevant
members or
pointers so an LP64 architecture actually would have the same member sizes as
a 32-bit architecture.
So if there's an LP64 architecture which has the same maxalign (presumably
64-bit for doubles) as its 32-bit cousin then it's actually possible we
wouldn't notice?
--
Gregory Stark
Gregory Stark [EMAIL PROTECTED] writes:
Oh, I see what you meant now. Datum is a purely in-memory concept, it doesn't
actually reach disk.
We could always tighten this up a bit by listing the alignment of a handful of
built-in data types but I suppose there will always be holes in this area
. Are we sure Slony et al don't use time_t or enums
or anything else which may have changed between these two runtimes?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast
Rainer Bauer [EMAIL PROTECTED] writes:
Gregory Stark wrote:
This is because of (at least) two changes in the ABI between the runtimes used
by mingw and VC++.
1) Enums are apparently 8 bytes on VC++ but 4 bytes on mingw
They are 4 bytes here on my 32 bit WinXP machine with VS2005SP1.
Oh, I
Simon Riggs [EMAIL PROTECTED] writes:
On Wed, 2007-12-05 at 08:24 +, Gregory Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
Simon Riggs [EMAIL PROTECTED] writes:
I'm thinking that there isn't any way currently of working out how big a
compressed toast object is?
pg_column_size
integer).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
701 - 800 of 1641 matches
Mail list logo