Hi,
On Mon, 2007-12-03 at 20:07 -0500, Tom Lane wrote:
> You need bigger TeX settings. Please read "Building the
> Documentation".
Thanks for the info. Apparently, those values are not enough. I'm still
trying to build pdf on my box.
BTW, I'll be happier if someone else can build the pdf from
Magnus Hagander wrote:
On Mon, 2007-12-03 at 12:15 -0500, Andrew Dunstan wrote:
Magnus Hagander wrote:
Hi!
When you redid the msvc build stuff you seem to have missed the
documentatino.. Specifically, I notice that buildenv.pl isn't documented -
docs still say buildenv.bat is the way
Hi all,
I have a patch which tries to improve the '\d some_sequence_name' command
output in psql utility. Before sending the patch to pgsql-patches I just want
to know your opinion whether the new output of the command is OK or it needs to
be modified before sending it to pgsql-patches.
For c
On 04/12/2007, Aftab Hussain <[EMAIL PROTECTED]> wrote:
>
>
> Hi all,
>
> I have a patch which tries to improve the '\d some_sequence_name' command
> output in psql utility. Before sending the patch to pgsql-patches I just
> want to know your opinion whether the new output of the command is OK or i
I'm thinking that there isn't any way currently of working out how big a
compressed toast object is?
All existing functions decompress the object before we do anything to
it, AFAICS. Am I missing something?
So there's no way currently of working out how good your compression is
for individual val
A simple query:
select prec.bl_considerada_prioritaria
AS "A proposta é considerada prioritária por Conselho Municipal ou Estadual"
from consultaprevia2008.tab_urb_asse_prec prec
The result: ERROR: invalid string enlargement request size 1073741823
But.. If i replace the accented char, leaving
Walter Cruz escribió:
> A simple query:
>
> select prec.bl_considerada_prioritaria
> AS "A proposta é considerada prioritária por Conselho Municipal ou Estadual"
> from consultaprevia2008.tab_urb_asse_prec prec
>
> The result: ERROR: invalid string enlargement request size 1073741823
Weird. Pr
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> The two interfaces I'm aware of for this are posix_fadvise() and libaio.
> I've run tests with a synthetic benchmark which generates a large file then
> reads a random selection of blocks from within it using either synchronous
> reads like we do now
Yes, encoding mismatch [:)]
"client_encoding";"UNICODE"
"lc_collate";"pt_BR.UTF-8"
"lc_ctype";"pt_BR.UTF-8"
"lc_messages";"pt_BR.UTF_8"
"lc_monetary";"pt_BR.UTF_8"
"lc_numeric";"pt_BR.UTF_8"
"lc_time";"pt_BR.UTF_8"
"server_encoding";"LATIN1"
I'm with some troubles to set the encoding In my PHP p
Gregory Stark wrote:
"Gregory Stark" <[EMAIL PROTECTED]> writes
The two interfaces I'm aware of for this are posix_fadvise() and libaio.
I've run tests with a synthetic benchmark which generates a large file then
reads a random selection of blocks from within it using either synchronous
reads li
"Mark Mielke" <[EMAIL PROTECTED]> writes:
> I didn't see exceeded 3X in the graph. But I certainly see 2X+ for most of the
> graphic, and ~3X for very small reads. Possibly, it is avoiding unnecessary
> read-ahead at the drive or OS levels?
Then you're misreading the graph -- which would be my fa
"Mark Mielke" <[EMAIL PROTECTED]> writes:
> I didn't see exceeded 3X in the graph. But I certainly see 2X+ for most of the
> graphic, and ~3X for very small reads. Possibly, it is avoiding unnecessary
> read-ahead at the drive or OS levels?
Ahh! I think I see how you're misreading it now. You're
"Walter Cruz" <[EMAIL PROTECTED]> writes:
> I posted on hackers cause I think that was a bug, os something.
Yeah, I think so too. Can you extract a reproducible test case?
regards, tom lane
---(end of broadcast)---
TIP 3: H
On Nov 15, 2007, at 4:41 AM, Gregory Stark wrote:
Ask me about EnterpriseDB's Slony Replication support!
Hah, wtf is that all about? :)
BTW, looked at londiste?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Dec 2007 16:41:52 -0600
Decibel! <[EMAIL PROTECTED]> wrote:
> On Nov 15, 2007, at 4:41 AM, Gregory Stark wrote:
> > Ask me about EnterpriseDB's Slony Replication support!
>
>
> Hah, wtf is that all about? :)
Stealth marketing :)...
Jos
On Dec 4, 2007, at 4:48 PM, Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Dec 2007 16:41:52 -0600
Decibel! <[EMAIL PROTECTED]> wrote:
On Nov 15, 2007, at 4:41 AM, Gregory Stark wrote:
Ask me about EnterpriseDB's Slony Replication support!
Hah, wtf is that
On Dec 4, 2007, at 1:42 PM, Gregory Stark wrote:
I'm debating between two ways to structure the code right now. Do I
put the
logic to peek ahead in nodeBitmapHeapScan to read ahead and
remember the info
seen or in tidbitmap with an new api function which is only really
useful for
this one u
"Decibel!" <[EMAIL PROTECTED]> writes:
> On Dec 4, 2007, at 1:42 PM, Gregory Stark wrote:
>> I'm debating between two ways to structure the code right now. Do I put the
>> logic to peek ahead in nodeBitmapHeapScan to read ahead and remember the
>> info
>> seen or in tidbitmap with an new api fun
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() ?
regards, tom lane
---(end of broadcast)---
TIP 4: Have you s
19 matches
Mail list logo