This is an old system that we converted over from Oracle just this past
year. The first 10 days of this year bit us when needed warehouse
tables were removed erroneously.
I'm going to push uphill against management to try and create the tables
as table_nameMMDD.
Wish me luck!
Thanks for all y
Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
9nth join or so, explain analyze became to show the plan with many
tables being read in sequential fashion. Of course, this slows down the
query response in a factor on 10.
I can alter the order in wich the join's are appended,
Gerardo Herzig writes:
> Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
> 9nth join or so, explain analyze became to show the plan with many
> tables being read in sequential fashion. Of course, this slows down the
> query response in a factor on 10.
increase join_collapse
El mié, 11-01-2012 a las 10:40 -0500, Tom Lane escribió:
> Gerardo Herzig writes:
> > Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
> > 9nth join or so, explain analyze became to show the plan with many
> > tables being read in sequential fashion. Of course, this slows dow
Gerardo Herzig writes:
> So, what happens, when a plsql function is excecuted, it takes is own
> enviroment variables, or something like that?
No, but it probably cached a plan from an execution before you changed
join_collapse_limit ...
regards, tom lane
--
Sent via pg
I have an issue I can't figure out. I have the following TABLE:
tysql=# \d customers
Table "public.customers"
Column| Type | Modifiers
--++---
cust_id | character(10) | not null
cust_name| character(50) | not null
cust_a
-Original Message-
From: pgsql-sql-ow...@postgresql.org [mailto:pgsql-sql-ow...@postgresql.org]
On Behalf Of Carlos Mennens
Sent: Wednesday, January 11, 2012 6:53 PM
To: PostgreSQL (SQL)
Subject: [SQL] Unable To Alter Data Type
Now I'm attempting to ALTER the field 'cust_zip' TYPE from ch
On Wed, Jan 11, 2012 at 7:13 PM, David Johnston wrote:
> However, I will say again, you DO NOT WANT TO ACTUALLY DO THIS!
>
> The specific issue is that some US Postal Code begin with a zero ( 0 ) and
> so whenever you want to the zip_code value you need to pad leading zeros if
> the length is less
On Jan 11, 2012, at 19:30, Carlos Mennens wrote:
> On Wed, Jan 11, 2012 at 7:13 PM, David Johnston wrote:
>> However, I will say again, you DO NOT WANT TO ACTUALLY DO THIS!
>>
>> The specific issue is that some US Postal Code begin with a zero ( 0 ) and
>> so whenever you want to the zip_code v
